> I had the same problem.  To fix it, I had to do two things....
> 
> First:   I had to update to CVS head, this was as per broadvoice
support.
> 
> Second:  After  updating, I had to change my sip.conf.  Originally my
> sip.conf used hard coded ip addresses for broadvoice's IP servers, so
I
> had to change the following lines as such:
> register => [mynumber]:[EMAIL PROTECTED]
> to read
> register => [mynumber]:[EMAIL PROTECTED]
> 


Ed,

Weird things...I took your advice but executed it in stages...just like
you, I was registering with 147.135.8.129, hardcoded ip. My CVS-HEAD is
7/14/04.

The only thing I changed so far is to replace the 147.135.8.129 with
sip.broadvoice.com.  I didn't update from CVS, I also don't have SRV
lookups enabled (yet anyway).  It now registers and I can receive
inbound calls.

Does it make sense that BV may have implemented a change that would
allow registrations from a FQDN but not from a hardcoded ip? Just a
thought....

Marty

_______________________________________________
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

Reply via email to