Andy Valencia
2009-Aug-02 00:01 UTC
[asterisk-users] Broadvoice versus Asterisk 1.4.25.1 and 1.4.26
--------------- Hi, I got hit with a funny one today; my configuration, which had been running fine for many weeks, suddenly stopped registering with Broadvoice's SIP. I switched among BV SIP hosts, verified my account was OK, even tried upgrading Asterisk. The weird thing was that I could associate OK with my WiFi SIP phone. So it looked like an Asterisk- specific SIP interoperability problem. I played with a lot of stuff, and ended up finding that enabling "qualify=yes" (my PBX isn't behind a NAT and thus doesn't need to keep NAT state warm) seems to make the REGISTER work. At least, changing that config element and then "sip reload" got my BV peering back. I'll send a note if I find out anything else. And I'd certainly like to hear from any other BV users who might have seen a recent change. Andy Valencia
Tom Browning
2009-Aug-02 00:56 UTC
[asterisk-users] Broadvoice versus Asterisk 1.4.25.1 and 1.4.26
FWIW, my broadvoice setup ( and I just upgraded to 1.4.26 to play with Skype channels and verified that Broadvoice still works ) register=781zzznnnn at sip.broadvoice.com:p assword:781zzznnnn at sip.broadvoice.com/781zzznnnn [sip.broadvoice.com] type=peer user=phone host=sip.broadvoice.com fromdomain=sip.broadvoice.com fromuser=781zzznnnn secret=password username=781zzznnnn authuser=781zzznnnn insecure=invite context=from-pstn dtmfmode=rfc2833 dtmf=rfc2833 callerid=781zzznnnn canreinvite=no (might be a couple bogus lines in there from long ago debugging efforts to get broadvoice to work) On Sat, Aug 1, 2009 at 8:01 PM, Andy Valencia <ajv-593-869-0750 at vsta.org>wrote:> --------------- > Hi, > > I got hit with a funny one today; my configuration, which had been > running fine for many weeks, suddenly stopped registering with > Broadvoice's SIP. I switched among BV SIP hosts, verified my account > was OK, even tried upgrading Asterisk. The weird thing was that I could > associate OK with my WiFi SIP phone. So it looked like an Asterisk- > specific SIP interoperability problem. > > I played with a lot of stuff, and ended up finding that enabling > "qualify=yes" (my PBX isn't behind a NAT and thus doesn't need to keep > NAT state warm) seems to make the REGISTER work. At least, changing > that config element and then "sip reload" got my BV peering back. > I'll send a note if I find out anything else. And I'd certainly like > to hear from any other BV users who might have seen a recent change. > > Andy Valencia > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2009 - October 13 - 15 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090801/dd976b12/attachment.htm