On Fri, Apr 3, 2009 at 6:34 PM, Dale Worley <[email protected]> wrote: > On Fri, 2009-04-03 at 17:05 -0400, M. Ranganathan wrote: >> Hello, >> >> Following up a discussion with Scott on #sipx, here is a trace where I >> am attempting the following scenario : >> >> incoming call from ITSP phone 201 rings >> Call pickup by Extension 202 >> Attempt to blind transfer to Extension 203. >> >> The INVITE on the blind transfer gets a challenge (407) response (note >> Frame 114 ) > > What is the SIP domain and realm of this system? > > I see that the REFER has "Refer-To: > <sip:[email protected]?x-sipx-authidentity=%3csip%3auser2% > 40example.local%3Bsignature%3D49D676F5%253A% > 253A746fa93df32a1de66fe4e0d87692f7eb%3E>". The blind transfer target is > "sip:[email protected]" but the authorization identity is > "sip:[email protected]". That suggests the realm is not the same as > the domain. That's OK, but we have to make sure that the generation and > detection of authidentities agrees on how to construct them. > > Dale
Hi Dale, According to domain-config : SIP_DOMAIN_NAME : example.local SIP_DOMAIN_ALIASES : 192.168.5.75 sipxtest.example.local SIP_REALM : example.local SHARED_SECRET : LaOdlm4g6MKKnbwAKIve9Geo DEFAULT_LANGUAGE : en SUPERVISOR_PORT : 8092 CONFIG_HOSTS : sipxtest.example.local The Refer target in this case : sip:[email protected] This is what SIpXbridge will put into the INVITE Request-URI The Refer-To is generated by the phone and modified by sipx proxy. Ranga > > > -- 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
