On Mon, Nov 24, 2008 at 10:57 AM, Scott Lawrence <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-11-24 at 10:11 -0500, M. Ranganathan wrote: >> On Mon, Nov 24, 2008 at 10:10 AM, Scott Lawrence >> <[EMAIL PROTECTED]> wrote: >> > >> >> >> >> 1. The inbound call arrives from an ITSP. It is answered by extension 203 >> >> 2. 203 parks the call ( REFER to extension 300 ) >> >> 3. 201 attempts to retrieve the call. > > While looking at the logs you sent for this problem, I noticed two > things that were problematic in the sipXbridge logging: > > 1) The INVITE sent as a result of the REFER was not logged (or at least > not in a way that sipx-trace could find). > > 2) The sipXbridge logs have chunks of binary in them - this confused the > 'grep' in sipx-trace. I've added a change that I'll check in later > today to address that in sipx-trace, but it's probably symptomatic of > some other problem. Log files should always be all text. > > >
Thanks to Robert, this problem is fixed. The issue is that sipxtacklib uses the entire From and To header as well as callId for dialog matching even if Tags are present in From and To headers. This is contrary to the recommendation of rfc 3261. -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
