Hi All, I noticed an error in my example below: The Sipx and Xlite responses were the wrong way around. Should be:
SIPX :Contact: <sip:[email protected]:5062>;LINEID=e27e3a08a40c;x-sipX-nonat XLITE:Contact: <sip:[email protected]:2228 ;rinstance=0cb1214fe2ba2461;transport=TCP;x-sipX-nonat> I am still stuck on this one. Has anybody encountered any problems using sipxCallRedirect()? TIA Mike On Fri, Nov 6, 2009 at 4:44 PM, Mike Hoare <[email protected]> wrote: > Hi, > > Has anyone else encountered the following: > > sipxTapi instance 1: registers Line [email protected] > sipxTapi instance 2: registers Line [email protected] > sipxTapi instance 3: registers Line [email protected] > > When a Call comes into 8000 it is redirected to 8001. > This call is then transferred to 8002. > > The transfer fails using sipxTapi. Blind or Consult. > But it works ok if x-lite (eyeBeam) is plugged in for 8001. > > Wireshark shows that the only major difference between doing this using > x-lite or sipxTapi is in the contact header of the SIP REFER: > > XLITE:Contact: <sip:[email protected]:5062>;LINEID=e27e3a08a40c;x-sipX-nonat > SIPX:Contact: <sip:[email protected]:2228 > ;rinstance=0cb1214fe2ba2461;transport=TCP;x-sipX-nonat> > > Any help greatly appreciated > > Mike >
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
