[Asterisk-Users] Re: Broadvoice configuration changes for outbound calls

[Brian Buhrow]

	Hello.  I'm not sure what's going on with the gentleman who is having
trouble receiving inbound calls as of this weekend, but I can say that
while inbound works for me, calling out through BroadVoice doesn't work at
all.  SIP traces show that when I send an invite request out to BroadVoice,
they send back a 401 unauthorized message which includes a
WWW-Authentication: header which ASterisk is supposed to use to send a
reply proxy authentication response.
	The version of Asterisk I'm running, and have been running with
BroadVoice for months claims that it sends an acknowledgement of the
unauthorized message, then fails to send an authentication reply, instead
claiming that authentication is impossible with BroadVoice.
	I suspect that there is a bug in the md5 hashing  code on the version
of Asterisk I'm running, and I'll be attempting to upgrade things, or sort
out the bug soon.
	My point here is to let people know that they may be seeing different
behaviors depending on what version of ASterisk code they're running.  I'm
running with CVS head as of 2003-12-18.  I doubt many others are running
code this old, but until this Saturday morning, it's worked flawlessly with
every provider I've tried it with.
	Having said all that, I too am disappointed that BroadVoice has not
seen fit to tell its users of this impending change.  Instead, it worked on
Friday night for me, all normal, and, voila! complete failure of outgoing
calls on Saturday morning.  Most disturbing.

Hope that's somewhat helpful.