Re: [reSIProcate-users] Request timeout logs

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

It may not be entirely obvious, but you can tell from the logs if a response has been receive off the wire or not, or has been internally generated.  There is also a flag on SipMessage that also tells you if amessage is from the wire or not:  SipMessage::isFromWire

No options for alternate behaviour exist today.

Scott

On Mon, Sep 22, 2014 at 12:56 PM, Jorge Bustamante <jbustamante@xxxxxxxxxxxxx> wrote:

Hi,

When our app sends a SIP request that doesn't get answered, it eventually times out and resiprocate auto-generates(fakes) a SIP 408 response and posts it back to our app - this is somewhat misleading because it makes reading the logs unreliable since one cannot discriminate real SIP messages from fake ones. Is there a way we can avoid this behaviour, e.g. running a timeout function instead of generating fake SIP responses?

Regards,

Jorge Bustamante

See why you should attend BroadSoft Connections 2014

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/