[SIPForum-discussion] strange behavior
Aniella Juverdeanu
Aniella.Juverdeanu at telus.com
Fri Feb 14 22:51:35 UTC 2014
I don't know what to say - one would need all details to get the entire picture. I do not quite understand why OPTIONS have the same call-ID as the Invite initiated calls. If OPTIONS are for keep alive then the call-ID should be different. OPTIONS is normal practice if you have alternate routes or at least alarm on SIP connection down. If for keep alive the OPTIONS messages should be present without any call between the nodes.
thanks
From: Vinicio Callejas [mailto:vinicio.callejas at gmail.com]
Sent: February 14, 2014 02:08 PM
To: Aniella Juverdeanu
Cc: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] strange behavior
Dear, the 3600 seconds timeout is set by us in our gear so we do not allow more than 3600 seconds of duration for a call to this destination. Question was if this behaviour of OPTIONS messages used as keep alive resource is normal behaviour or not?
and if we disable the OPTIONS messges in our gear will this affect these kind of calls decreasing ASR for example?
Thanks a lot.
Vinicio
2014-02-14 15:41 GMT-06:00 Vinicio Callejas <vinicio.callejas at gmail.com<mailto:vinicio.callejas at gmail.com>>:
Hello Aniella and Stephen,
Thanks a lot for the reply it is very appreciated, i searched and yes the OPTION messages and INVITE have the same Call ID and tag=xxxxx
OPTION MESSAGE CALL ID: 7f8ad28d3278c3d1ab1bac5b059e879f at SoftX3000
INVITE MESSAGE CALL ID: 7f8ad28d3278c3d1ab1bac5b059e879f at SoftX3000
OPTION MESSAGE TAG: <sip:026515615981190 at 192.168.1.1<mailto:sip%3A026515615981190 at 192.168.1.1>;user=phone>;tag=40a32ecb-CC-23
INVITE MESSAGE TAG: <sip:026515615981190 at 192.168.1.1<mailto:sip%3A026515615981190 at 192.168.1.1>;user=phone>;tag=40a32ecb-CC-23
Note: i chaged the original IP :)
Question:
1) So this call should be charged to customer right? this is a valid call?
2) We own the middle equipment so if we disable the OPTION messages will this affect these kind of call completion?
We are worried because we see many calls with release code as "Maximum Time Exceeded" with 3600 seconds, all calls with this code have duration of 3600 seconds, is this normal?
Please advise.
Thanks a lot!
Vinicio
2014-02-14 15:24 GMT-06:00 Aniella Juverdeanu <Aniella.Juverdeanu at telus.com<mailto:Aniella.Juverdeanu at telus.com>>:
Isn't this OPTIONS just enabled between the two SIP nodes for keep alive? I think they repeat at a regular interval - Wireshark just captures them - this is normal practice if you have an alternate IP address for the destination. Please check call-ID to see if OPTIONS are part of the initial call.
Thanks,
Aniella
From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org>] On Behalf Of Vinicio Callejas
Sent: February 14, 2014 09:53 AM
To: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: [SIPForum-discussion] strange behavior
Dear SIP-Forum community,
I need their valuable help in my next question in the following trace:
|Time | 192.168.222.1 |
| | | 172.16.0.8 |
|0.000000 | INVITE SDP (g729 telephone-eventRTPType-101) |SIP From: <sip:026515615981190 at 200.30.79.27<mailto:sip%3A026515615981190 at 200.30.79.27>;user=phone To:<sip:76750257231163 at 192.168.222.1<mailto:sip%3A76750257231163 at 192.168.222.1>;user=phone
| |(5062) ------------------> (5060) |
|0.001112 | 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|0.283508 | 183 Progress |SIP Status
| |(5062) <------------------ (5060) |
|2.153476 | 183 Progress SDP (g729 telephone-eventRTPType-...) |SIP Status
| |(5062) <------------------ (5060) |
|3.072989 | 180 Ringing |SIP Status
| |(5062) <------------------ (5060) |
|9.686369 | 200 OK SDP (g729 telephone-eventRTPType-101) |SIP Status
| |(5062) <------------------ (5060) |
|9.951822 | ACK | |SIP Request
| |(5062) ------------------> (5060) |
|9.951834 | OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|10.152405| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|10.172826| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|369.954905| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|370.156250| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|370.182409| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|730.015937| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|730.216594| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|730.234521| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|1089.969163| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|1090.173824| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|1090.183164| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|1449.971924| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|1450.172387| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|1450.203957| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|1809.984631| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|1810.188181| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|1810.204932| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|2169.987896<tel:2169.987896>| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|2170.188157| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|2170.206157| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|2529.991223<tel:2529.991223>| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|2530.192339| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|2530.230736| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|2889.994229| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|2890.196896| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|2890.216868| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|3250.006942| OPTIONS | |SIP Request
| |(5062) ------------------> (5060) |
|3250.209311| 100 Trying| |SIP Status
| |(5062) <------------------ (5060) |
|3250.236541| 200 Ok SDP () |SIP Status
| |(5062) <------------------ (5060) |
|3609.689094<tel:3609.689094>| BYE | |SIP Request
| |(5062) <------------------ (5060) |
|3609.910220<tel:3609.910220>| 200 OK | |SIP Status
| |(5062) ------------------> (5060) |
My question is this because after ACK there are so many options that are generated.
Could someone explain the reason for this situation, if there are problems in the codec or a bad configuration?
Best Regards,
Vinicio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20140214/853086b6/attachment-0002.html>
More information about the discussion
mailing list