Hi All, With a change to the Avaya config which I've updated on the wiki, I can now do a blind transfer to a conference!
Cheers Arne On Wed, Oct 28, 2009 at 6:03 PM, shouldbe q931 <shouldbeq...@googlemail.com> wrote: > Apologies if I'm reading like an idiot (well, at best an uneducated > person), but I'm still bothered by this. > > I can see that for each of the two cases sipXecs is sending a > different REFER, my point was why does the extension just have the > domain name, while the conference has the full hostname ? > > Also if I dial the conference directly, the INVITE just has the domain > name, and it connects... > > As an aside, I've opened an Avaya ticket to see why they are changing > the target. I probably won't have a sensible response for a few days, > but... > > Cheers > > Arne > > On Wed, Oct 28, 2009 at 5:28 PM, Scott Lawrence > <scott.lawre...@nortel.com> wrote: >> On Wed, 2009-10-28 at 14:59 +0000, shouldbe q931 wrote: >>> Point taken. >>> >>> Does that mean that when the "transfer" to 6810 happens as per the >>> attached pcap, where it just uses the domain rather than the F.Q.D.N >>> is incorrect ? >> >> No, it's correct because in that trace the Refer-To header is: >> >> Refer-To: "68 >> 10"<sip:6...@loewygroup.local?x-sipx-authidentity=%3csip%3a%7e%7eid%7emedia%40loewygroup.local%3bsignature%3d4ae85c06%253a%253a0570fbee949747e2a6db55f60843aea3%3e> >> >> which becomes: >> >> INVITE sip:6...@loewygroup.local SIP/2.0 >> X-sipX-Authidentity: >> <sip:~~id~me...@loewygroup.local;signature=4AE85C06%3A%3A0570fbee949747e2a6db55f60843aea3> >> >> just as it is supposed to. >> >> The transfer target URL that's sent for your conference is to the host >> name, and so that's what the Avaya should be sending. >> >> > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
