Daniel Petrie wrote: > I am not sure which connection you are referring to. These appear to > be UDP transported SIP messages. The REGISTER request has nothing to > do with the BYE transaction. It is merely a timing coinsidence. The > sipX client is not resending the BYE with digest credentials most > likely because it is not provisioned with credentials for the > sip.ub2.cae.local realm. >
Sipxtacklib was given credentials for the sip.ub2.cae.local realm, as it resent REGISTER (after 401) and INVITE (after 407) for the same realm. But it didn't resend a BYE after 407. I also wonder whether transport=tls in received contact could cause any confusion in sipxtacklib as it was compiled without TLS support (TLS is not fully functional in sipxtapi branch as far as I know, it only works in the main branch). I'm attaching a wireshark dump where the problem can be clearly seen. Jaro
AvayaCall.pcap
Description: Binary data
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
