asterisk users - Mar 2005 - BroadVoice configuration changes for Outbound

Today, We have added INVITE Authentication.  This seems to bring a large 
amount of problems to people in the way since they can't make outbound 
calls.  Here's what needs to be done.  You need to add three variables to 
your peers or friends, username, authuser, and secret.

username=<phonenumber>
authuser=<phonenumber>
secret=<registration password>

Dan

Thanks for this info, Dan!  I noticed immediately that outbound was broken, and 
inbound was OK.  I saw your posting just prior to going berserk...  a warning 
email from Broadvoice would have been nice, they knew to email me when that 
SIP-patch from edvina came out some months ago.

Anyway, thanks for the posting!

Jerry

On Sat, 5 Mar 2005, Dan Weber wrote:
> Today, We have added INVITE Authentication.  This seems to bring a large 
> amount of problems to people in the way since they can't make outbound
calls.
> Here's what needs to be done.  You need to add three variables to your
peers
> or friends, username, authuser, and secret.
>
> username=<phonenumber>
> authuser=<phonenumber>
> secret=<registration password>
>
> Dan

An Open letter to Broadvoice from an Asterisk user...

(This is not a solicitation for support from the Asterisk list.  The
specifics of my problems have already been emailed to their support
team.)

May I suggest:

1) Updating your website that tells how to configure Asterisk for Broadvoice.

2) Answering emails to support@broadvoice.com.

3) Emailing your users that signed up as BYOB when you think a change
might break stuff.


I *really* want to be a happy Broadvoice user.  Your willingness to
openly support Asterisk users is a huge selling point and the thing
that gives you an edge in my mind.

As an "early adopter" kinda guy, I'm happy to tweak stuff to make
things work.  I can't however explain to my wife why the phone doesn't
work *again*.  I'm going to hang in there a bit longer in hopes that
things will get better, if they don't, it's off to another VSP.

Best Wishes,
Gabe

On Sat, 5 Mar 2005 12:13:08 -0500 (EST), Dan Weber <dan@mirrorlynx.com>
wrote:
> Today, We have added INVITE Authentication.  This seems to bring a large
> amount of problems to people in the way since they can't make outbound
> calls.  Here's what needs to be done.  You need to add three variables
to
> your peers or friends, username, authuser, and secret.
> 
> username=<phonenumber>
> authuser=<phonenumber>
> secret=<registration password>
> 
> Dan

On Sat, 5 Mar 2005 12:13:08 -0500 (EST), Dan Weber <dan@mirrorlynx.com>
wrote:
> Today, We have added INVITE Authentication.  
Thanks for the warning. You pissed my wife off. If she can't make
calls, she's an unhappy camper. Maybe next time you warn us?

Sheesh....

-Chuji

Why can't Broadvoice just LEAVE WELL ENOUGH ALONE!!!!!!  Now, after 
applying these new variables, I can't receive INCOMING calls.  Sheesh, 
what a bunch of BS!!  Now we have to spend another weekend fixing what 
BV screws up.


Dan Weber wrote:
> Today, We have added INVITE Authentication.  This seems to bring a 
> large amount of problems to people in the way since they can't make 
> outbound calls.  Here's what needs to be done.  You need to add three 
> variables to your peers or friends, username, authuser, and secret.
>
> username=<phonenumber>
> authuser=<phonenumber>
> secret=<registration password>
>
> Dan
>

In the last email I sent, I did not mean to insult anyone, but I have 
tested the instructions thoroughly I provided.  If you were using the 
instructions I provided originally, you would not be able to make outbound 
calls.  Here are the instructions that have been known to work;
Please read line by line and setup that way.

http://foo.robotics.net/mediawiki-1.3.10/index.php/Asterisk_Setup

Dan

On Sun, 6 Mar 2005, skamp wrote:
> sorry still doesnt help with incoming calls, there is definatley
> something more wrong, my config was working fine until today and its
> worked fine for months. They have broken something.
>
> On Sun, 2005-03-06 at 02:23 -0600, Bartosz Wegrzyn - asterisk wrote:
>> [broadvoice-incoming]
>> type=peer
>> host=147.135.8.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
>>
>> [broadvoice-incoming2]
>> type=peer
>> host=147.135.0.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
>>
>> [broadvoice-incoming3]
>> type=peer
>> host=147.135.4.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
> -- 
> skamp <skamp@arkayinc.com>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

can u send your config and simple description of your network

Bart
> sorry still doesnt help with incoming calls, there is definatley
> something more wrong, my config was working fine until today and its
> worked fine for months. They have broken something.
>
> On Sun, 2005-03-06 at 02:23 -0600, Bartosz Wegrzyn - asterisk wrote:
>> [broadvoice-incoming]
>> type=peer
>> host=147.135.8.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
>>
>> [broadvoice-incoming2]
>> type=peer
>> host=147.135.0.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
>>
>> [broadvoice-incoming3]
>> type=peer
>> host=147.135.4.128
>> context=from-broadvoice
>> qualify=yes
>> canreinvite=no
>> disallow=all
>> allow=ulaw
>> nat=never
> --
> skamp <skamp@arkayinc.com>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

Doing this with no notification whatsoever, let alone notification
sufficiently in advance of these changes, was stupid and careless. This
move probably broke a significant number of your customers' telephones
service. One can only guess at the impact that this careless move had on
your customer service department.

In the future, give some thought to planning such changes more
carefully, announcing them well in advance of implemenatation. 

I am satisfied enough with my BroadVoice service that I will overlook
this incident, but there are lots of other vendors out there. Surely, at
least one of them has more concern for their customers than BroadVoice
has demonstrated with this fiasco.
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Dan Weber
> Sent: Saturday, March 05, 2005 9:13 AM
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] BroadVoice configuration changes 
> for Outbound
> 
> 
> Today, We have added INVITE Authentication.  This seems to 
> bring a large 
> amount of problems to people in the way since they can't make 
> outbound 
> calls.  Here's what needs to be done.  You need to add three 
> variables to 
> your peers or friends, username, authuser, and secret.
> 
> username=<phonenumber>
> authuser=<phonenumber>
> secret=<registration password>
> 
> Dan
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com 
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To 
> UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.6.0 - Release Date: 03/02/2005
>  
> 
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.6.0 - Release Date: 03/02/2005