Jaroslav Libak wrote: > Pedro Sanchez wrote: >> Jaroslav Libak wrote: >>> Pedro Sanchez wrote: >>>> Jaroslav Libak wrote: >>>>> Pedro Sanchez wrote: >>>>>> Hello, >>>>>> >>>>>> I'm about to start working on a project which requires some SIP >>>>>> libraries to be linked into an application. I am considering using the >>>>>> sipXtapi library and as a first step I want to verify that I can >>>>>> register to my SIP proxies using some already existent sipXtapi-based >>>>>> SIP clients. >>>>>> >>>>>> Reading the archives of this list I came across CrossTalk >>>>>> (http://www.sgssoft.com/crosstalk/crosstalk.asp) and wxCommunicator >>>>>> (http://wxcommunicator.sourceforge.net). Both programs however fail to >>>>>> register in identical manner, which makes me think about a problem >>>>>> with >>>>>> the sipXtapi library in the first place. But of course, it could be a >>>>>> configuration issue or something else. >>>>>> >>>>>> I have attached a very simple wireshark trace of the SIP negotiation >>>>>> between these clients and my proxy. Basically the clients quit when >>>>>> they >>>>>> receive a 407 "Proxy Authentication Required" message from the proxy. >>>>>> For comparison, I also include another trace of the openwengo SIP >>>>>> client >>>>>> (http://openwengo.org) which succeeds with the registration. >>>>>> >>>>>> I would appreciate any comments on this problem. Also, if you can >>>>>> suggest other sipXtapi-based SIP clients worth testing that would be >>>>>> great. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>> Did you provide the correct realm? The correct realm for wxCommunicator >>>>> and crosstalk for this provider is Realm. Please try to set realm to >>>>> Realm, and report what's happening in SipUserAgent line 1773 where we >>>>> respond to HTTP_UNAUTHORIZED_CODE and HTTP_PROXY_UNAUTHORIZED_CODE. >>>>> >>>>> Jaro >>>>> >>>> I changed the realm value to "Realm" (it was "nortel.com") as indicated, >>>> thanks. Crosstalk succeeds and I can establish a phone call, even though >>>> I have to manually append '@nortel.com" to each number I want to dial. >>>> >>>> On the other hand wxCommunicator goes a couple of steps further but it >>>> still fails to register. See attachment. >>>> >>>> As for reporting what happens on line 1773 I'm afraid I can't do it at >>>> this moment. I'm using the pre-compiled binaries of the SIP clients that >>>> I downloaded from the projects' web sites. I'm not yet at the point of >>>> compiling from source. >>>> >>>> wxCommunicator gets into a loop trying to register filling my desktop >>>> with little error windows telling me about an "unknown cause" for >>>> failing to register. This is the log: >>>> >>>> 15:52:12: SipXTapiProxy::OnSipxInitializeResult - Sipx initialization >>>> successful for profile [EMAIL PROTECTED] >>>> 15:52:12: SipXTapiProxy::SipXConfigureAudio - Audio was configured >>>> successfuly >>>> 15:52:12: AsyncProxyThread::OnSipxConfigureSip - OnSipxConfigureSip >>>> event received >>>> 15:52:12: AsyncProxyThread::OnSipxConfigureSip - Using default >>>> contact ID >>>> 15:52:12: AsyncProxyThread::ChooseDesiredContactID - SIP Contact list: >>>> 15:52:12: AsyncProxyThread::ChooseDesiredContactID - >>>> Id: 1 >>>> Contact type: local >>>> Transport type: udp >>>> Source interface: eth1 >>>> IP address: 47.129.110.47 >>>> Port 5060 >>>> >>>> 15:52:12: AsyncProxyThread::ChooseDesiredContactID - >>>> Id: 2 >>>> Contact type: local >>>> Transport type: tcp >>>> Source interface: eth1 >>>> IP address: 47.129.110.47 >>>> Port 5060 >>>> >>>> 15:52:12: PhoneLineEventHandler::PrintEventString - LineEvent received >>>> -1:1: PROVISIONED::PROVISIONED_NORMAL >>>> 15:52:12: AsyncProxyThread::CreateLine - sipxLineAdd Line 1 >>>> succeeded >>>> 15:52:12: AsyncProxyThread::CreateLine - sipxLineAddCredential >>>> Line 1 succeeded >>>> 15:52:12: PhoneLineEventHandler::PrintEventString - LineEvent received >>>> 0:1: REGISTERING::REGISTERING_NORMAL >>>> 15:52:12: AsyncProxyThread::CreateLine - sipxLineRegister Line 1 >>>> succeeded >>>> 15:52:12: Error: AsyncProxyThread::OnSipxConfigureSip - >>>> sipxConfigEnableRTCP failed, error code 1 >>>> 15:52:12: Error: AsyncProxyThread::OnSipxConfigureSip - >>>> sipxConfigEnableOutOfBandDTMF failed, error code 1 >>>> 15:52:12: PhoneLineEventHandler::PrintEventString - LineEvent received >>>> 0:1: REGISTER_FAILED::CAUSE_UNKNOWN >>>> >>>> >>> You probably set something wrong in wxCommunicator. Could you send me >>> wireshark trace of SIP communication when using crosstalk and >>> wxCommunicator? wxCommunicator uses the same sipXtapi, I would say >>> perhaps a more recent version, and is much more configurable. >>> >>> Jaro >> I have the outbound proxy defined in the "Basic" tab of the SIP profile >> editor. Also, this is my wxCommunicator line config info: >> >> Line 1 >> ------ >> name: Line 1 >> Line URI: psanchez >> Username: psanchez >> Password: ***** >> Realm: Realm >> "Register line with sip proxy" is checked. >> >> Attached you will find the two traces. >> >> >> Thanks, >> >> > > The register expiration period is too short. Go to edit sip profile -> > Expert "tab" -> set "register expiration time to a higher value (120 or > more). It is 2nd time somebody has a problem with this setting. The > default value is so low, so that it acts as keep alive for NAT mapping. > The solution is to use real keep alive from sipxtapi in wxCommunicator. > I think crosstalk doesn't use keepalive either, but uses different > default values. I have tested keepalive using unittests and it seems to > be working so there is no reason not to use it. > > Jaro > Thanks Jaro, it does work with this modification!
My next step is going to be to compile wxCommunicator from source as per the instructions in the project's web site. One thing that worries me is the mention to "Download patched sipXtapi source code ..." in step 2. But I will ask about it in a different thread so that we can close this one. Thank you again, -- Pedro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
