Solved: SIP Trunk transfers to voicemail and auto attendent

Douglas Yoder · ‎08-31-2010

Having issues with my dial-peers and voice translation rules converting from a PRI to SIP trunk (see attached).

Steven Holl · ‎09-01-2010

CUE isn't responding to the INVITE which it is being sent. Are you sure that you can ping 192.168.69.200 from CME? If you've changed the IP on CUE recently, have to reloaded CUE since then?

Here is the INVITE to CUE which gets no response:

Sep 1 11:50:50.279: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:100@192.168.69.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.69.1:5060;branch=z9hG4bK191EC85
From: "Cell Phone OH" <xxxxxx6147>;tag=7BFBDF1C-16CF
To: <100>
Date: Wed, 01 Sep 2010 11:50:50 GMT
Call-ID: 33E18E-B4F611DF-B3CAECE3-E844E7D7@192.168.69.1
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 3360103-3036025311-3016158435-3896829911
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1283341850
Contact: <xxxxxx6147>
Call-Info: <192.168.69.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Diversion: <203>;privacy=off;reason=no-answer;screen=no
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 4166 5167 IN IP4 192.168.69.1
s=SIP Call
c=IN IP4 192.168.69.1
t=0 0
m=audio 17818 RTP/AVP 0
c=IN IP4 192.168.69.1
a=rtpmap:0 PCMU/8000
a=ptime:20

View solution in original post

Steven Holl · ‎09-01-2010

What is the specific issue which you are seeing? Just attaching a configuration and saying you are having a problem isn't enough for someone to help you fix your issue.

Run the following debugs during a call failure:

debug voip ccapi inout

debug ccsip mess

Douglas Yoder · ‎09-01-2010

Sorry about that, here is the debug and when the call gets transferred to AA or Voicemail the system returns a "all circuits are busy" message.

Steven Holl · ‎09-01-2010

CUE isn't responding to the INVITE which it is being sent. Are you sure that you can ping 192.168.69.200 from CME? If you've changed the IP on CUE recently, have to reloaded CUE since then?

Here is the INVITE to CUE which gets no response:

Sep 1 11:50:50.279: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:100@192.168.69.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.69.1:5060;branch=z9hG4bK191EC85
From: "Cell Phone OH" <xxxxxx6147>;tag=7BFBDF1C-16CF
To: <100>
Date: Wed, 01 Sep 2010 11:50:50 GMT
Call-ID: 33E18E-B4F611DF-B3CAECE3-E844E7D7@192.168.69.1
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 3360103-3036025311-3016158435-3896829911
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1283341850
Contact: <xxxxxx6147>
Call-Info: <192.168.69.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Diversion: <203>;privacy=off;reason=no-answer;screen=no
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 4166 5167 IN IP4 192.168.69.1
s=SIP Call
c=IN IP4 192.168.69.1
t=0 0
m=audio 17818 RTP/AVP 0
c=IN IP4 192.168.69.1
a=rtpmap:0 PCMU/8000
a=ptime:20

Douglas Yoder · ‎09-01-2010

That was it, got a little carried away with the static routes and accidently routed the CUE to the SIP Trunk. Removed that and all is good. After a late night working on this I figured it was something simple I was over looking. Thanks Steve.