On Sun, 2009-03-08 at 11:57 -0400, M. Ranganathan wrote:
> On Fri, Mar 6, 2009 at 8:13 PM, M. Ranganathan <[email protected]> wrote:
> > The scenario is :
> >
> > Sipxbridge sends an inbound call to the operator
> > Operator refers the call to extension 203.
> > Extension 201 tries to pick up the call.
> >
> > If I dont redirect the call from the operator -- i.e. try to directly
> > send the call to 203 and then do the pick up when 203 is ringing, it
> > works fine. 201 is able to pick up the call.
> >
> > However, if I redirect the call and then attempt to do the pickup it fails.
> >
> > On Frame 113 of the attached trace notice that the registrar returns a
> > 302 with a Contact: Unknown URL scheme.
> >
> > Any ideas what might be happening here?
> >
> > Note that the local case works fine. So this is possibly something I
> > am doing wrong in SIPXBRIDGE
>
> It turns out you have to user a userName in the contact header SIP URI
> of the REFER. Why is this the case?
That's not quite the problem - the problem is that the URL was:
sip:@192.168.5.75:5090
... the presence of the @ means that there should be a user part -
that's not a valid url because it has an @ but no user part. That
breaks the url parser. When the redirector used it as input to
construct a contact, the parse failed, but the redirector evidently did
not test for that failure (the way to do that test it to check the url
scheme of the Url object - for a failed parse, it will return an unknown
scheme value).
The LG phone got sent this in the INVITE:
INVITE sip:[email protected]:5060;x-sipX-nonat SIP/2.0
User-Agent: sipXecs/3.11.11 sipXecs/sipxbridge (Linux)
Contact: <sip:192.168.5.75:5090;x-sipX-nonat>
... which was perfectly OK - no @ in the contact, so no user part. But
when it sent a dialog event notice for that ringing dialog, it sent the
more limited contact above (it also removed the url parameter, which is
also incorrect - one should not mess with other peoples tokens).
So... there are at least two bugs in the LG phone firmware, but you can
work around at least one of them by putting a user part in.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
