[SIPForum-discussion] doubt about "contact field"

Knupp, Varlei Fernandes varlei.knupp at siemens.com
Thu Mar 22 15:30:32 UTC 2007



Hi to all,

I have a doubt about "contact field".

The proxy send a "INVITE" message =INVITE sip:33133010 at 192.168.2.100:5060 SIP/2.0 to Gateway

The gateway send  a "session progress" message to proxy, but this message has contact field = Contact: <sip:1100 at 192.168.2.100>

The User disconnect the call.

The proxy send a "CANCEL" message to gateway = CANCEL sip:1100 at 192.168.2.100:5060 SIP/2.0 

So the gateway reject the message.

Who is correct?
- The Gateway because reject the call because the proxy changed the header in the message CANCEL
- The Proxy because when the gateway sent contact field = <sip:1100 at 192.168.2.100> the header CANCEL message now is  CANCEL sip:1100 at 192.168.2.100:5060 SIP/2.0.

thanks a lot


Varlei Fernandes Knupp

SIEMENS Communications

Customer Services Enterprise

RCC São Paulo - Technical Support

Tel.: +55 11 3817 2659

Fax: +55 11 3817 2613

varlei.knupp at siemens.com <blocked::mailto:varlei.knupp at siemens.com>




________________________________________
The information contained in this e-mail is for the exclusive use of the intended recipient(s) and may be confidential, proprietary, and/or legally privileged.  Inadvertent disclosure of this message does not constitute a waiver of any privilege.  If you receive this message in error, please do not directly or indirectly use, print, copy, forward, or disclose any part of this message.  Please also delete this e-mail and all copies and notify the sender. Thank you. For alternate languages please go to http://www.siemens.com.ar/disclaimer/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070322/cef9d0b9/attachment-0002.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CANCEL.txt
URL: <http://sipforum.org/pipermail/discussion/attachments/20070322/cef9d0b9/attachment-0002.txt>


More information about the discussion mailing list