07-25-2008 11:00 PM - edited 03-18-2019 09:22 PM
My CUE has been working for months. Recently it stops responding to AA and voicemail calls. Debug on cme shows sip invite is sent correctly to cue, by no reponse received.
==============
000567: Jul 26 18:46:46.594: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:7999@10.216.1.253:5060 SIP/2.0
Via: SIP/2.0/UDP 202.162.180.9:5060;branch=z9hG4bK455CB
From: "Spare" <sip:5554@202.162.180.9>;tag=471FF6C-1E48
To: <sip:7999@10.216.1.253>
Date: Sat, 26 Jul 2008 06:46:46 GMT
Call-ID: 73481F44-5A1511DD-80A4F928-E5F7CCFC@202.162.180.9
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1923626420-1511330269-2157967656-3858222332
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SU
tt-triton-cme#BSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1217054806
Contact: <sip:5554@202.162.180.9:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250
v=0
o=CiscoSystemsSIP-GW-UserAgent 2324 9168 IN IP4 202.162.180.9
s=SIP Call
c=IN IP4 202.162.180.9
t=0 0
m=audio 17590 RTP/AVP 0 101
c=IN IP4 202.162.180.9
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
==================
Debug on cue shows nothing (not receiving any sip invite).
=============
trace ccn trace ccn stacksip dbug
trace ccn managerappl dbug
trace ccn libmedia dbug
trace ccn subsystemcmt dbug
show trace buffer tail
================
But VoiceView is working fine.
Any ideas?
Thanks in advance.
Solved! Go to Solution.
07-26-2008 01:37 PM
reload the entire router, and verify its still broken. After please upload the config. I am going to suggest a TAC Case though, because equipment does break and if there were 0 changes, and its been working for months. I would firstly assume a broken CUE.
HTH,
Chad
07-26-2008 01:37 PM
reload the entire router, and verify its still broken. After please upload the config. I am going to suggest a TAC Case though, because equipment does break and if there were 0 changes, and its been working for months. I would firstly assume a broken CUE.
HTH,
Chad
07-28-2008 01:47 PM
Thanks a lot. Problem resolved.
01-15-2009 02:27 PM
Larry,
Can you tell what the solution of the problem was? Was it the CME/CUE reload?
Thank you.
01-15-2009 02:56 PM
Hi Bartosz,
Just a simple rebooting did the job.
Rgd.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide