[VoiceOps] Metaswitch challenging SIP BYE

Alex Balashov abalashov at evaristesys.com
Thu Sep 29 21:33:03 EDT 2011

Yeah, I know.  But as you know, it's not always about the standards, but what's de facto in the field.  Think 3261 requirement for every stack to support TCP transport. :-)

This message was painstakingly thumbed out on my mobile, so apologies for brevity, errors, and general sloppiness.

Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/

On Sep 29, 2011, at 8:53 PM, Jimmy Hess <mysidia at gmail.com> wrote:

> On Wed, Sep 28, 2011 at 4:22 PM, Alex Balashov
> <abalashov at evaristesys.com> wrote:
>> On 09/28/2011 05:19 PM, Mark Holloway wrote:
>> I wonder how common it is to auth-challenge sequential requests across the
>> board.  There is considerable and spirited debate as to whether it's a good
>> idea, or whether it should be done only for initial requests.
> A user agent not prepared to cope with auth challenge of BYE or any
> SIP message excepting
> CANCEL and ACK  is not correctly implementing SIP authentication as
> specified by RFC3261
> and should be fixed....
> --
> -JH

More information about the VoiceOps mailing list