[Freeswitch-users] How to get the content of SIP headers

[Jon Bruel]

As I see it, the NOTIFY methods mentioned are used when there is a call,
i.e. at the earliest when the phone has responded with a RINGING or a
similar response to the INVITE. By the way, the response to the INVITE
also includes a list of events (Header: Allow-Events) which the phone
responds to. I have not seen other instances where the NOTIFY To-header
needs to be tagged, but my experience is limited and not bound to the
RFCs, so don't rely on me!

On Sep 18, 2008, at 4:53 AM, Jon Bruel wrote:

> Thank you for your replies. In checking the SIP messaging sequence,  
> I saw that you are right about the source of the tag to the To- 
> header: it is the phone, which as a response to the INVITE, adds the  
> tag (and not, as I wrote, the FreeSWITCH). Still, we need a way to  
> read it, and not the least to send NOTIFYs with the right tag. I  
> have raised two issues on the Jira, maybe the category is wrong.
>
> One of the tricky things to sort out is how to handle it in the case  
> of bridging to a list of devices, and bridging to a user with  
> multiple registrations. The NOTIFY method should include measures to  
> send a NOTIFY to a specific phone among the many phones responding.
>
> Thanks again for your excellent responsiveness ? it adds the trust  
> of the FreeSWITCH.   Jon.
>
So we would only have the to tag in the case of a device with a call  
in progress, what about for just a registration, how would you  
determine between the devices?

Mike