Log In
Developer Network
Technologies
Join the Network
Member Services
Events & Community
Unified Communications Manager SIP (SIP) Developer Center
Overview
Documentation
Community
Wiki
Testing
Everything
This Site
Blogs
9.1 SIP Documentation Now Available
Adrienne Moherek
10 Jan 2013
Unified Communications 9.0 Partner Bundle Offer Now Available to Order
Amanda Whaley
21 Sep 2012
Update - Silent Monitoring/Recording Supported Devices
George Gary
31 Aug 2012
Developer Partner 2012 US Update Presentations Available
George Gary
29 Jun 2012
Developer Partner 2012 London Update Presentations Available
George Gary
10 Feb 2012
Showing 1 - 5 of 21 results.
Items per Page 5
Page
(Changing the value of this field will reload the page.)
1
2
3
4
5
of 5
First
Previous
Next
Last
Forums
Message Boards Home
Recent Posts
Statistics
Answer
(
Unmark
)
Mark as an Answer
« Back to SIP Trunk Questions
CUCM sends INVITE after 900 sec
Threads [
Previous
|
Next
]
CUCM sends INVITE after 900 sec
Sascha Monteiro
1/19/12 5:29 AM
RE: CUCM sends INVITE after 900 sec
Abdul Rasheed
1/19/12 6:38 AM
RE: CUCM sends INVITE after 900 sec
Sascha Monteiro
1/20/12 1:34 AM
RE: CUCM sends INVITE after 900 sec
David Staudt
1/21/12 12:20 AM
RE: CUCM sends INVITE after 900 sec
Dan-Anders Hook
1/19/12 2:23 PM
Sascha Monteiro
Posts:
4
Join Date:
10/6/08
Recent Posts
CUCM sends INVITE after 900 sec
cucm
sip
sip trunk
recording
Answer
1/19/12 5:29 AM
Mark as an Answer
Submit
Reply with Quote
Quick Reply
Hi,
We have built a Recorder that receives calls via a SIP trunk (recording profile) through the IPPhone's built in bridge
It works fine until the call gets to 900 seconds, we receive another INVITE and it looks like our app sends a Trying,
then CUCM sends BYE
I could not find this behaviour in SIP docs, is it a keep-alive? Should CUCM send this? What should happen?
This is a wireshark trace from our server, appreciate any feedback!
Attachments:
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Abdul Rasheed
Posts:
13
Join Date:
3/5/09
Recent Posts
RE: CUCM sends INVITE after 900 sec
Answer
1/19/12 6:38 AM as a reply to Sascha Monteiro.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
Hello,
which is the version of your call manager? what is the reason of BYE in wireshark?
Best regards
Rasheed
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Dan-Anders Hook
Posts:
2
Join Date:
2/18/09
Recent Posts
RE: CUCM sends INVITE after 900 sec
Answer
1/19/12 2:23 PM as a reply to Sascha Monteiro.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
Hi,
Sounds like interop problems with session refresh. Try changing the CUCM Service parameter "SIP Session Expires Timer". A refresh is sent after half this time, and the default is 1800 sec. I have changed this to 86400 (max) for some customers due to the same reason.
Kind regards,
//Dan
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Sascha Monteiro
Posts:
4
Join Date:
10/6/08
Recent Posts
RE: CUCM sends INVITE after 900 sec
Answer
1/20/12 1:34 AM as a reply to Abdul Rasheed.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
cucm7.1
this is from wireshark;
BYE sip:9.1.1.222:5060;transport=tcp SIP/2.0
Route: <sip:9.1.1.222:5060;transport=tcp;appname=CiscoStreamingRecorder;final_response=true;lr>
Reason: Q.850;cause=86
Date: Wed, 18 Jan 2012 21:23:04 GMT
From: "TK" <sip:45@9.1.1.71;x-nearend;x-refci=17435925;x-nearenddevice=SEP002584179241>;tag=ea21c2f9-ce2a-413c-a933-cb6751cb8e6c-17435930
Content-Length: 0
User-Agent: Cisco-CUCM7.1
To: <sip:911222@9.1.1.222>;tag=3585576
Call-ID: 810c8100-f17134b3-9bf3-47010109@9.1.1.71
Via: SIP/2.0/TCP 9.1.1.71:5060;branch=z9hG4bK9c6c5c46eb4d
P-Preferred-Identity: "TK" <sip:45@9.1.1.71>
CSeq: 103 BYE
Max-Forwards: 70
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
David Staudt
Posts:
18
Join Date:
6/4/08
Recent Posts
RE: CUCM sends INVITE after 900 sec
Answer
1/21/12 12:20 AM as a reply to Sascha Monteiro.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
cause=86 looks to be Network Timeout, so I agree the SIP session refresh mechanim mentioned above is likely the root cause. I guess you can either modify the recorder side to interop with the way UCM does this refresh, or modify the timer so that in practice it never occurs (as above.)
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Collateral
No files available