I've just gotten the box to register all 4-ports with an external SIP provider. The provider is running an old release of Broadsoft backend. Seems like Broadsoft supports this strange way of authentication.
the 3504As do work with welltech's SIP proxy servers as well.
i checked the authentication code in chan_sip.c, and discovered that asterisk keeps track of the nonce (aka md5 hashed token) it sends out to registering users. when the users resend the register packet with the auth credentials, asterisk uses the Call-ID (or Call-ID and tag attribute if pedantic=yes) to match the second register packet with it's kept state to get the nonce it sent out the first time.
according to the RFC, different SIP users should be using different Call-IDs. as each of the 3504A's FXS ports register individually, they thus should be using different Call-IDs, however they don't but rather reuse the same Call-IDs. this is the behaviour which confuses asterisk as the wellgate registers.
(like i mentioned before, this is based on my reading of the RFC. i'm no SIP guru, so i may well be wrong in this analysis)
-- Regards, /\_/\ "All dogs go to heaven." [EMAIL PROTECTED] (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
