Renan Panes rdpanes at yahoo.com
Thu Jun 23 11:16:55 UTC 2011

Hi Gonzalo,

This scenario happened just now, and it never occured with any of my previous 
trunks. I found the culprit and the peer IP address is left restricted in one of 
our firewalls and that causes my SIP INVITE message to get re-transmitted for 
several attempts until it finally timed out.

Multiple SIP INVITE had been eliminated now, yet I am getting a new SIP error 
422 (Session Timer Too Small) from peer end which I believe an adjustment to be 
done on their side.

Thank you all for the comments, appreciated much.


Best Regards,
Renan Panes
Email:    rdpanes at yahoo.com
IM:        rdpanes

From: Gonzalo Gasca <gogasca at cisco.com>
To: Renan Panes <rdpanes at yahoo.com>; discussion at sipforum.org
Sent: Thursday, June 23, 2011 7:48:49
Subject: Re: [SIPForum-discussion] MULTIPLE SIP INVITE MESSAGE

Re: [SIPForum-discussion] MULTIPLE SIP INVITE MESSAGE Hi Renan,

I will trust only a network packet capture.
Multiple applications, (example CUCM 8.6, Cisco CTX) may display same message 
twice or more time in logs but that doesn’t mean we are getting the same INVITE 
message. It just how your application is coded to display information.
Is this happening all the time? Or Is there a problem cause by this?


Gonzalo Gasca

From: Renan Panes <rdpanes at yahoo.com>
Date: Wed, 22 Jun 2011 04:19:40 -0700 (PDT)
To: <discussion at sipforum.org>
Subject: [SIPForum-discussion] MULTIPLE SIP INVITE MESSAGE

Hello Forum,

Multiple SIP Invite Message sending is seen on my trace logs, how does this 
happen and why?

Appreciate any advise and recommendations. Thanks.


Best Regards,


Renan Panes

Email:    rdpanes at yahoo.com

IM:        rdpanes

This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit 
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20110623/b09e4db9/attachment-0002.html>

More information about the discussion mailing list