Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Busy calls dropped by CUE/AA

Hi Folks,

I have got an CUE/AA setup on a 2911 which is working as expected.

I can dial into the AA and hear the prompts etc.

However, when i try to transfer the call to another extension i get the following:

     Available: Success (no issues with call / transfers)

     Busy: Fail - call is dropped

     Unavailable: Fail - call is dropped

In the ccsip messages debug i can see the following:

Jul 18 14:10:55.159: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 18 14:10:55.163: Content-Type: audio/telephone-event

01 00 07 D0

Jul 18 14:10:55.163: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:4539@192.168.50.20:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK29536A0

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

To: <sip:4539@192.168.50.20>;tag=dsa6091600

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

CSeq: 102 NOTIFY

Max-Forwards: 70

Date: Thu, 18 Jul 2013 14:10:55 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:192.168.50.19:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 18 14:10:55.163: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK29536A0

To: <sip:4539@192.168.50.20>;tag=dsa6091600

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

CSeq: 102 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: message-summary

Allow-Events: telephone-event

Jul 18 14:10:55.223: //-1/xxxxxxxxxxxx/SIP/Msg/sipDisplayBinaryData:

Sending: Binary Message Body

Jul 18 14:10:55.223: Content-Type: audio/telephone-event

01 80 00 50

Jul 18 14:10:55.223: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:4539@192.168.50.20:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK2954120C

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

To: <sip:4539@192.168.50.20>;tag=dsa6091600

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

CSeq: 103 NOTIFY

Max-Forwards: 70

Date: Thu, 18 Jul 2013 14:10:55 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:192.168.50.19:5060>

Content-Type: audio/telephone-event

Content-Length: 4

.P

Jul 18 14:10:55.223: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK2954120C

To: <sip:4539@192.168.50.20>;tag=dsa6091600

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

CSeq: 103 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: message-summary

Allow-Events: telephone-event

Jul 18 14:11:01.315: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:4512@192.168.50.19:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.50.20:5060;branch=z9hG4bKHnVI.m4gzev.hQ5rssySOw~~4

Max-Forwards: 70

To: <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

From: <sip:4539@192.168.50.20>;tag=dsa6091600

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

CSeq: 2 BYE

Content-Length: 0

Also: <sip:4865@192.168.50.19:5060;user=phone>

Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO

Cisco-Gcid: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

Jul 18 14:11:01.315: //16847/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.50.20:5060;branch=z9hG4bKHnVI.m4gzev.hQ5rssySOw~~4

From: <sip:4539@192.168.50.20>;tag=dsa6091600

To: "4512" <sip:4512@192.168.50.19>;tag=1C4DD26C-3F2

Date: Thu, 18 Jul 2013 14:11:01 GMT

Call-ID: AFF91B1B-EEEA11E2-80C3DC8E-99EF951C@192.168.50.19

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 2 BYE

P-RTP-Stat: PS=483,OS=76032,PR=481,OR=76801,PL=0,JI=0,LA=0,DU=9

Content-Length: 0

Jul 18 14:11:01.319: //16852/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:4865@192.168.50.50:5061 SIP/2.0

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295619C

Remote-Party-ID: "4512" <sip:4512@192.168.50.19>;party=calling;screen=no;privacy=off

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DF824-EBB

To: <sip:4865@192.168.50.50>

Date: Thu, 18 Jul 2013 14:11:01 GMT

Call-ID: B5BA7EEF-EEEA11E2-80C6DC8E-99EF951C@192.168.50.19

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 2952258251-4008317410-2159926414-2582615324

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Timestamp: 1374156661

Contact: <sip:4512@192.168.50.19:5060>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 69

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 249

v=0

o=CiscoSystemsSIP-GW-UserAgent 6030 398 IN IP4 192.168.50.19

s=SIP Call

c=IN IP4 192.168.50.19

t=0 0

m=audio 19620 RTP/AVP 0 101

c=IN IP4 192.168.50.19

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Jul 18 14:11:01.323: //16852/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295619C

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DF824-EBB

To: <sip:4865@192.168.50.50>;tag=17721048

Date: Thu, 18 Jul 2013 14:01:09 GMT

Call-ID: B5BA7EEF-EEEA11E2-80C6DC8E-99EF951C@192.168.50.19

Timestamp: 1374156661

CSeq: 101 INVITE

Allow-Events: telephone-event

Content-Length: 0

Jul 18 14:11:01.335: //16852/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 486 Busy here

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295619C

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DF824-EBB

To: <sip:4865@192.168.50.50>;tag=17721048

Date: Thu, 18 Jul 2013 14:01:09 GMT

Call-ID: B5BA7EEF-EEEA11E2-80C6DC8E-99EF951C@192.168.50.19

Timestamp: 1374156661

CSeq: 101 INVITE

Allow-Events: telephone-event

Content-Length: 0

Jul 18 14:11:01.339: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:4865@192.168.50.50:5061 SIP/2.0

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295619C

From: "4512" <sip:4512@192.168.50.19>;tag=1C4DF824-EBB

To: <sip:4865@192.168.50.50>;tag=17721048

Date: Thu, 18 Jul 2013 14:11:01 GMT

Call-ID: B5BA7EEF-EEEA11E2-80C6DC8E-99EF951C@192.168.50.19

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Jul 18 14:11:01.339: //16846/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:4512@192.168.42.30:18444 SIP/2.0

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295721A2

From: "4539"<sip:4539@192.168.50.19>;tag=1C4DD278-1308

To: "4512"<sip:4512@192.168.50.19>;tag=713bc85f

Date: Thu, 18 Jul 2013 14:10:51 GMT

Call-ID: MjFhMThlZGZhZTVlY2MzNGE4NGQwMzFjYjcwM2I5ZTY.

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1374156661

CSeq: 101 BYE

Reason: Q.850;cause=17

P-RTP-Stat: PS=481,OS=76801,PR=485,OR=76352,PL=0,JI=0,LA=0,DU=9

Content-Length: 0

Jul 18 14:11:01.479: //16846/AFF7E2CB80BD/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.50.19:5060;branch=z9hG4bK295721A2

Contact: <sip:4512@192.168.42.30:18444>

To: "4512"<sip:4512@192.168.50.19>;tag=713bc85f

From: "4539"<sip:4539@192.168.50.19>;tag=1C4DD278-1308

Call-ID: MjFhMThlZGZhZTVlY2MzNGE4NGQwMzFjYjcwM2I5ZTY.

CSeq: 101 BYE

User-Agent: X-Lite release 1011s stamp 41150

Content-Length: 0

Any help would be most appreciated!

5 REPLIES
New Member

Busy calls dropped by CUE/AA

If the call-flow is required:

4865 <----> CUCM <----> SIP TRUNK <----> CME <----> CUE <----> 4939 (AA)

I have tested this from another handset within CME and the call is still dropped when a busy tone is received.

Busy calls dropped by CUE/AA

What is the CME/CUE version?

If this is hapenning for all calls, we should take a look on CUE, please capture:

show license status application

--
Jorge Armijo

Please remember to rate helpful responses and identify helpful or correct answers.

-- Jorge Armijo Please remember to rate helpful responses and identify helpful or correct answers.
New Member

Busy calls dropped by CUE/AA

Hi Jorge,

The current versions are:

     CME: c2900-universalk9-mz.SPA.151-4.M4.bin

     CUE: 8.6.4 (Running on a SM-SRE-719-K9)

License information for CME is:

     ipbase      ipbasek9     permanent

     uc            uck9           permanent

License information for CUE is:

     voicemail enabled: 12 ports, 8 sessions, 5 mailboxes

New Member

Re: Busy calls dropped by CUE/AA

If this helps, the CUCM is version 4.1(3) and runs a hardware based MTP on a 2621xm (IOS: 12.4.15(T5))

I have also attached the trace from CUE of a call from 4512 to 4865 using the Auto Attendant (ServiceDesk)

Also attached a better diagram.

New Member

Re: Busy calls dropped by CUE/AA

Can anybody help at all?

Whilst doing a reactive script on CUE i can see that the call instantly goes to Successful on the Redirect funciton. It is like it is doing a blind transfer.

316
Views
0
Helpful
5
Replies
CreatePlease login to create content