I've analyzed the second Invite request. SipXtapi seems to use the to-header to assign the call to a line. The Invite request header is addressed to 709. The to-header is adressed to 710. Because the expected address can be found in the request uri I tried to get it with sipxCallGetRequestURI. I wanted to check if the uri is the uri of my masterline and adjust the program behavior. The problem is, that sipxCallGetRequestURI returns an empty string until sipxCallAnswer is executed and CALLSTATE_CONNECTED received. This is too late. Isn't it illogical that the request uri of the invite is not available before the 200OK is send?
Thanks in advance... Jan Thiemo Fricke schrieb: > Hi there, > I'm using sipxtapi for a softphone with multiple lines. > The first line is the "masterline" for the softphone user. > That means it is used by the softphone user for outgoing/incoming cals. > > The other lines are just registered to monitor and pickup calls of other > phones easy. (The lines are registered on other phones also). > > The display of the caller should show that the softphone has pickedup > the call and the cdrs on sipx server should show the correct caller and > callee. The solution also should be server and enddevice independent. > (Which implicate that presence service and sipx functions can't be used) > > The idea was to redirect the call of the monitored line to the > "masterline". But that does not work. > > Line 1 (masterline) number 709 > Line 2 (monitorline) number 710 > . > . > . > Line n (monitorline)... > > Here is the use-case: > > 1. A call is ariving at the monitored line 2 with the number 710. > 2. sipxCallRedirect(hCall, "7...@mydomain.de"); is executed. > 3. Wirshark shows the moved temporarily to 709 which is the masterline. > 4. The old call to 710 on line two is destroyed. > 5. Invite to 7...@mydomain.de arives. > > BUT when the next CALLSTATE_NEWCALL event arrives the parameter hLine is > 2 although the calls goes to 709 which is associated to line 1. > > If I call 709 directly hLine has the correct number (1). > > > I would be very grateful for some help! > > Best regards > Jan > > _______________________________________________ > sipxtapi-dev mailing list > sipxtapi-dev@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ > _______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
