cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
985
Views
0
Helpful
1
Replies

Getting Error on CME Disconnect cause 38 & 503

nayeem111
Level 1
Level 1

Am trying to call from CME to CUCM getting the below error. Calling from CUCM to CME is successful.

 

Below are the logs while calling from CME to CUCM(Version-7) which is not successful.

 

Please advise.

 

015022: Sep 30 15:18:56.787: //218719/4EA4AE8283FB/SIP/Call/sipSPICallInfo:

The Call Setup Information is:

Call Control Block (CCB) : 0x0x7FBEC2648010

State of The Call : STATE_DEAD

TCP Sockets Used : NO

Calling Number : 4814

Called Number : 73230

Source IP Address (Sig ): 192.168.200.200

Destn SIP Req Addr:Port : 172.30.200.10:5060

Destn SIP Resp Addr:Port : 172.30.200.10:5060

Destination Name : 172.30.200.10

 

015023: Sep 30 15:18:56.787: //218719/4EA4AE8283FB/SIP/Call/sipSPIMediaCallInfo:

Number of Media Streams: 1

Media Stream : 1

Negotiated Codec : No Codec

Negotiated Codec Bytes : 0

Nego. Codec payload : 255 (tx), 255 (rx)

Negotiated Dtmf-relay : 0

Dtmf-relay Payload : 0 (tx), 0 (rx)

Source IP Address (Media): 192.168.200.200

Source IP Port (Media): 28950

Destn IP Address (Media): -

Destn IP Port (Media): 0

Orig Destn IP Address:Port (Media): [ - ]:0

 

015024: Sep 30 15:18:56.787: //218719/4EA4AE8283FB/SIP/Call/sipSPICallInfo:

Disconnect Cause (CC) : 38

Disconnect Cause (SIP) : 503

1 Reply 1

Error 38 means that your CME can't reach CUCM. Start with debug ip tcp
transactions to see what is happening when you initiate a connection
assuming that you use TCP SIP.

Check if there is anything blocking the connectivity and make sure the CME
is added to CUCM as SIP Trunk.

**** remember to rate useful posts
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: