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 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
