Re: [Sip-implementors] Multiple path headers in Request

[Dushyant Dhalia]

1. Path header is used by the Registrar to route the terminating initial 
requests.
2. There is no need to reject with 400. It's perfectly fine to receive 
multiple Path headers.
3. Use the received Path header in forming Route header whenever any 
request which needs to be terminated to <sip:u...@examplehome.com> 
arrives at the registrar sip:REGISTRAR.EXAMPLEHOME.COM

Dushyant P S Dhalia
priyank luthra wrote:
Hi
What would be the behaviour of a proxy/Registrar receiving a REGISTER with
multiple path headers, like
    REGISTER sip:REGISTRAR.EXAMPLEHOME.COM SIP/2.0
      Via: SIP/2.0/UDP 112.68.155.4:5060;branch=z9hG4bK34ghi7ab04
      Via: SIP/2.0/UDP 192.0.2.4:5060;branch=z9hG4bKnashds7
      To: UA1 <sip:u...@examplehome.com>
      From: UA1 <sip:u...@examplehome.com>;tag=456248
      Call-ID: 843817637684...@998sdasdh09
      CSeq: 1826 REGISTER
      Contact: <sip:u...@192.0.2.4 <sip%3a...@192.0.2.4>>
      Supported: path
      Path: <sip:P1.EXAMPLEVISITED.COM;lr>
      Path: <sip:proxy1.home.com;lr>
      Path: <sip:proxy2.home.com;lr>

Should this be treated the same way as if there was a single path
header with comma separated values ? Or should it return 400 BAD
request ?



  
<<attachment: dushyant_dhalia.vcf>>_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors