[SIPForum-discussion] Carrying additional information in a SIPmessage.

[Eric Burger]

Of course, the 3GPP folks might get a little upset about a P- header.  
Likewise, the IETF says you may not use a P- header unless you  
register it.

On Oct 20, 2009, at 10:57 PM, prasanna c wrote:

> Hi Ayyanar,
>
> There is no reason for the SIP proxies to remove the private headers  
> before forwarding, unless the header is not properly constructed.  
> Please send me the entire SIP message that your device sent out to  
> the proxy.
>
> Regards,
> Prasanna
>
> To: eburger at sipforum.org
> CC: c_prasanna_c at hotmail.com; discussion at sipforum.org
> From: pkayyanar at in.com
> Date: Tue, 20 Oct 2009 17:22:29 +0530
> Subject: Re: [SIPForum-discussion] Carrying additional information  
> in a SIPmessage.
>
> Hi Prasanna and Eric,
>
> The SIP Stack that we use has a provision to add a private to send  
> only between our products.
> The header is something like
>
> P-CompanyName-BusinessUnit. I added this header to the INVITE sent  
> from one device to another through a Public SIP Trunk. It seems like  
> the public SIP operators
> which are acting like proxies are not forwarding this header. What  
> am I supposed to do here ?
>
> The Call has to travel through a public SIP Trunk in that case can't  
> I send a proprietary message from one of my device to another which  
> are located at different places and connected by internet.
>
> Please give your suggestions. What else can I do ?
>
> Regards,
> Ayyanar
>
>
> ---------- Original message ----------
> From:Eric Burger< eburger at sipforum.org >
> Date: 19 Oct 09 16:04:56
> Subject: Re: [SIPForum- discussion] Carrying additional information  
> in a SIPmessage.
> To: prasanna c
>
> Yes, but no.
>
> Yes, anyone can put an arbitrary header into a SIP message. Most SIP  
> UAs will ignore it. Poor implementations will crash or worse.
>
> No, no one should put an arbitrary header into a SIP message. What  
> if you use "new:" to mean "here is a new feature" whereas the  
> recipient UA uses "new:" to mean "wipe the device."
>
> On Oct 18, 2009, at 1:40 PM, prasanna c wrote:
>
> Do you mean we cannot just introduce new headers (ex : "new : 1234\r  
> ") into SIP messages? In my understanding this is possible, as all  
> the SIP elements which do NOT understand this header MUST simply  
> ignore it.
>
>
> CC: pkayyanar at in.com; discussion at sipforum.org
> From: eburger at sipforum.org
> To: c_prasanna_c at hotmail.com
> Subject: Re: [SIPForum-discussion] Carrying additional information  
> in a SIP message.
> Date: Sat, 17 Oct 2009 18:33:01 -04 00
>
> Do realize there is no arbitrary ability to add headers willy-nilly,  
> like X- headers in email.
>
> You can always register an INFO package.
>
> On Oct 15, 2009, at 1:13 PM, prasanna c wrote:
>
> Hi,
>
> + Yes, you can carry any information in a SIP message. You can  
> introduce your SIP header to carry the IP address and the port number.
> + If the requirement is just to pass on the IP address & port  
> number, then you may want to use INFO SIP message, without  
> establishing any call.
>
> Regards,
> Prasanna
>
> To: discussion at sipforum.org
> From: pkayyanar at in.com
> Date: Wed, 14 Oct 2009 17:35:41 +0530
> Subject: [SIPForum-discussion] Carrying additional information in a  
> SIP message.
>
> Hi all,
>
> I have a requirement like, an IP address and a port number is got  
> from an external application which has to be carried in a SIP  
> message to another gateway. This additional information like IP and  
> port is used by another application on the remote gateway side to  
> establish a TCP connection to the gateway which initiated the SIP  
> Call.
>
> Now my question is
>
> 1. Is it possible to carry any additional information in a SIP  
> message.
> 2. If so which app ropriate SIP message can be used.
> 3. How can I differentiate between a normal SIP Call(voice call) and  
> this Call which carries additional information.
>
> The constraint is the gateway which initiated the SIP Call, should  
> also disconnect the call, on dissconect the remote gateway which  
> established a TCP connection will disconnect the TCP connection too.
>
>
> Example:
>
> Remote Gateway 1 Remote Gateway2
>
> ---------- INVITE (SIP Message)----------------&g t;
> To
> Additional Info:
> IP and port
>
> <----------200 OK-------------------------------------
>
> ------------ACK---------------------------------------->
>
> <---------- Open TCP Connection------------------
>
> <----------BYE--------------------------------------------
>
> -----------200OK---------------------------------------->
>
> <----------Close TCP Connection ------------------
>
> Note: The SIP mess age used in this example is only to demonstrate  
> the scenario.
>
> Please let me know if there any specific SIP request that can carry  
> additional user information.
>
>
> Dear discussion ! Get Yourself a cool, short @in.com Email ID now!
>
> Don’t fall behind. Log on to MSN India for a roundup on the world  
> panorama_______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
> Don’t fall behind. Log on to MSN India for a roundup on the world  
> panorama
>
>
> Don’t fall behind. Log on to MSN India for a roundup on the world  
> panorama

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20091022/588b7367/attachment-0002.html>