________________________________________ From: [email protected] [[email protected]] On Behalf Of [email protected] [[email protected]]
(Maybe more a SIP question then a SipX question) I am trying to get my Tandberg Cisco C40 codec under control. Every second call it makes fails. Wireshark showed me that with every second call the C40 makes it sends the authentication nonces in the first INVITE (so without being challenged by the proxy). SipX still replies with a "407 Proxy authentication required" (and new nonce), the C40 still "ACK's" the 407 but doesn't like it and stops communicating. Is the behavior of SipX right, I mean sending the 407 as a reply on an INVITE with authentication in it? As far as I know and can find in RFC's the client always has to send a "normal" INVITE first, then gets a "407 Proxy authentication required" and then it sends an INVITE with the nonces. If this is indeed the case then the C40 is misbehaving. ________________________________________ It revolves around the nonces. The C40 is using whichever nonce it previously received, in the hope that the nonce will be valid for the new call. This is a good strategy, as if it works, it will eliminate one round-trip. But sipX's nonces depend on the Call-Id and from-tag of the INVITE, and so nonces are specific to each dialog. Thus, the C40's clever attempt fails, and sipX sends a 407 response containing a nonce that will work for that INVITE. Since the C40's first attempt received a 407, it should try again, using the nonce it received in the 407. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
