[OpenSIPS-Users] multiple Via headers separated by comma

[Bogdan-Andrei Iancu]

Hi Josip,

Post both the BYE (sent out by opesips) and 200 OK (received by 
opensips)  in plain text .

Regards,
Bogdan

Josip Djuricic wrote:
> Hi Andrew,
>
> Thanks very much for your quick answer, I understand that by rfc it is
> completely valid.
>
> What I can't seem to find is why is my last 200 OK from uas not beeing
> matched against the BYE that opensips forwarded to uas. So after uas sends
> 200 OK, it keeps receiveing BYE until timeout occurs. It only happens with
> sipp, if using any other uac everything works as expected. Every other
> transaction is matched correctly.
>
> I'm includig siplog from that last message, with changed ip's.
>
> Perhaps you would see this problem more clearly?
>
> Thanks,
>
> Josip
>
>
>
>
> -----Original Message-----
> From: users-bounces at lists.opensips.org
> [mailto:users-bounces at lists.opensips.org] On Behalf Of Andrew Pogrebennyk
> Sent: Monday, December 21, 2009 10:44 AM
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] multiple Via headers separated by comma
>
> Josip Djuricic wrote:
>   
>> Transaction is not matched if request is sent with 2 or more multiline via
>> headers and response is received with via header in one line separated by
>> comma?
>>     
>
> Josip,
> This is absolutely legal if multiple values are combined in one line 
> separated by comma. Ccheck RFC 3261 for multiple header field values 
> combining.
>
> Section 7.3.
>     [H4.2] also specifies that multiple header fields of the same field
>     name whose value is a comma-separated list can be combined into one
>     header field.  That applies to SIP as well, but the specific rule is
>     different because of the different grammars.  Specifically, any SIP
>     header whose grammar is of the form
>
>        header  =  "header-name" HCOLON header-value *(COMMA header-value)
>
>     allows for combining header fields of the same name into a comma-
>     separated list.  The Contact header field allows a comma-separated
>     list unless the header field value is "*".
>
> Response is matched to request using branch parameter from uppermost Via 
> header, so I don't know why RFC compliant implementation would have 
> problems with response matching when Via header is combined.
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-- 
Bogdan-Andrei Iancu
www.voice-system.ro