Hi Keerthi

Yes, Subscribe may have multiple Contacts.
As per "draft-roach-sip-subscribe-notify-01":-

5.1.4 Subscriber SUBSCRIBE Behavior

     When a subscriber wishes to subscribe to (or refresh a
     subscription to) an event class, he forms a SUBSCRIBE message. If
     the subscription is call related, the call leg information (To,
     From, Call-ID) are used in the SUBSCRIBE message as if it were
     any other request related to the call.

     For non-call-related subscriptions, the call leg information is
     formed as if for an original INVITE: the Call-ID is a new call ID
     with the syntax described in RFC 2543; the To: field indicates
     the suscribed resource's persistent address (which will generally
     match the Request URI used to form the message); and the From:
     field will indicate the subscriber's persistent address
     (typically sip:user@machine for UAs, or sip:machine for other
     entities).

     In both circumstances, the Contact: header(s) will contain
     information about where resulting NOTIFY requests are to be sent.
     Multiple Contact headers are allowed, and indicate multiple
     destinations to which NOTIFY requests should be sent.

Refer : http://tools.ietf.org/html/draft-roach-sip-subscribe-notify-01


Regards
Preksha

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Keerthi 
Srinivasan
Sent: Tuesday, November 06, 2012 3:51 PM
To: [email protected]; [email protected]
Subject: [Sip-implementors] SUBSCRIBE request having multiple contact header

All,

Is the SUBSCRIBE request can have the multiple contact headers?

--
Regards,
Keerthi
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to