[OpenSER-Devel] question about 302 message

Watkins, Bradley Bradley.Watkins at compuware.com
Fri Jun 29 14:02:43 CEST 2007

You may want to follow Klaus' advice and use the q parameter.  You may
also want to examine the formatting of the first example in Section
20.10 of RFC3261.  It's possible that, barring a more lengthy
explanation somewhere else (which I haven't found in other RFCs at a
cursory glance), the UAs are being more pedantic about multiple URIs in
the Contact header.

- Brad 

> -----Original Message-----
> From: devel-bounces at openser.org 
> [mailto:devel-bounces at openser.org] On Behalf Of Di-Shi Sun
> Sent: Thursday, June 28, 2007 11:16 PM
> To: devel at openser.org
> Cc: Support of TransNexus
> Subject: [OpenSER-Devel] question about 302 message
> All,
> We did a test for OpenSER working as a redirect server. It 
> returns a 302 message with 2 destinations in the Contact 
> header ("Contact: 2222222222 at 
> <mailto:2222222222 at> , 2222222222 at"). 
> It looks fine. We want the source device to try the first 
> destination and do failover to the next destination if 
> necessary according to rfc 3261. But no a source device we 
> tried can handle it correctly.
> 1. Snom 360 softphone only try the first destination. After 
> the destination returned 404, the softphone stopped the call.
> 2. X-Lite softphone only try the second destination. After 
> the destination returned 404, the softphone stopped the call.
> 3. Asterisk cannot handle a Contact header with 2 URIs. We 
> posted a patch to make it only try the first destination.
> 4. Cisco 2600 IP/IP gateway also cannot handle it perperly.
> Did anybody have the experience for this test case? What 
> source device should be used?
> Thanks,
> Di-Shi Sun.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 

More information about the Devel mailing list