[Asterisk-Users] Anyone else having Broadvoice Problems?

[Marty Mastera]

> 
> I have also been having problems today registering...  I contacted
them,
> but
> they have no known issues.   It finally did register on it's own.
> 

For those having trouble with BV, try this for a test: in sip.conf,
replace occurrences of sip.broadvoice.com with this IP: 147.135.0.129,
explanation follows...

I just got off the phone with BV support who said they are having some
hardware issues on the west coast which should be fixed sometime in the
morning on Thursday.

Interestingly, he said that despite this problem there are hundreds of
asterisk users currently registering without any problems.  They
suggested that maybe some users are specifying IP addresses instead of
FQDNs in their sip.conf, foiling BV's "failover" capabilities.  I *do*
use a FQDN and still have no outbound calling working (inbound seems to
work - albeit intermittently).

In my testing, I noticed that a DNS query on sip.broadvoice.com returns
two addresses: 147.135.8.129 and 147.135.0.129, with the .8.129 address
being returned more often than the other...if I replace references to
sip.broadvoice.com in sip.conf with the second address (147.135.0.129)
my outbound calling starts working again.

Could this possibly indicate a problem with asterisk where the first
address resolved from sip.broadvoice.com isn't functioning correctly,
and asterisk doesn't try the alternate address? This isn't a scientific
analysis...just proposing an idea....I don't know enough about the
internals to make a statement like this, I'm hoping that someone out
there can provide more intelligent analysis of this!


This also makes me wonder if the "hundreds" of other asterisk users who
are registering correctly despite the hardware problem *are* using IP
addresses instead of sip.broadvoice.com and just happen to have used the
IP that is still working?

Marty