topic Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers in Unified Communications Infrastructure

SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Wed, 16 Mar 2022 09:17:25 GMT

Below is the log.

CUBE#
*Mar 16 08:10:49.090: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:08028800563@10.10.15.43:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK567c81a717cb6
From: "KAY" <sip:015150200@10.10.15.80>;tag=9887924~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18451251
To: <sip:08028800563@10.10.15.43>
Date: Wed, 16 Mar 2022 09:03:23 GMT
Call-ID: ed7f8500-2311a7db-4313e-500f0a0a@10.10.15.80
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Session-ID: 0e990365d0e3eeed8516a46aa9887923;remote=00000000000000000000000000000000
Cisco-Guid: 3984557312-0000065536-0000014087-1343162890
Session-Expires: 1800
P-Asserted-Identity: "KAY" <sip:015150200@10.10.15.80>
Remote-Party-ID: "KAY" <sip:015150200@10.10.15.80>;party=calling;screen=yes;privacy=off
Contact: <sip:015150200@10.10.15.80:5060;transport=tcp>
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 201

v=0
o=CiscoSystemsCCM-SIP 9887924 1 IN IP4 10.10.15.80
s=SIP Call
c=IN IP4 10.10.15.80
t=0 0
m=audio 29670 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Mar 16 08:10:49.098: //6089/ED7F85000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK567c81a717cb6
From: "KAY" <sip:015150200@10.10.15.80>;tag=9887924~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18451251
To: <sip:08028800563@10.10.15.43>
Date: Wed, 16 Mar 2022 08:10:49 GMT
Call-ID: ed7f8500-2311a7db-4313e-500f0a0a@10.10.15.80
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Content-Length: 0

*Mar 16 08:10:49.102: //6091/ED7F85000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08028800563@41.138.163.34:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKAB0122B
Remote-Party-ID: "KAY" <sip:015150200@10.10.15.43>;party=calling;screen=yes;privacy=off
From: "KAY" <sip:015150200@sip.cyberspace.com>;tag=23C66228-1F54
To: <sip:08028800563@41.138.163.34>
Date: Wed, 16 Mar 2022 08:10:49 GMT
Call-ID: 6C6F334D-A43711EC-A02BC069-6D87FBFC@10.10.15.43
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3984557312-0000065536-0000014087-1343162890
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1647418249
Contact: <sip:015150200@10.10.15.43:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 243

v=0
o=CiscoSystemsSIP-GW-UserAgent 1854 901 IN IP4 10.10.15.43
s=SIP Call
c=IN IP4 10.10.15.43
t=0 0
m=audio 22070 RTP/AVP 0 101
c=IN IP4 10.10.15.43
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

*Mar 16 08:10:49.106: //6091/ED7F85000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKAB0122B
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 6C6F334D-A43711EC-A02BC069-6D87FBFC@10.10.15.43
To: <sip:08028800563@41.138.163.34>
From: "KAY" <sip:015150200@sip.cyberspace.com>;tag=23C66228-1F54

*Mar 16 08:10:51.078: //6091/ED7F85000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKAB0122B
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 6C6F334D-A43711EC-A02BC069-6D87FBFC@10.10.15.43
To: <sip:08028800563@41.138.163.34>;tag=1003482543428890
From: "KAY" <sip:015150200@sip.cyberspace.com>;tag=23C66228-1F54

*Mar 16 08:10:51.078: //6089/ED7F85000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK567c81a717cb6
From: "KAY" <sip:015150200@10.10.15.80>;tag=9887924~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18451251
To: <sip:08028800563@10.10.15.43>;tag=23C669E0-1335
Date: Wed, 16 Mar 2022 08:10:49 GMT
Call-ID: ed7f8500-2311a7db-4313e-500f0a0a@10.10.15.80
CSeq: 101 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.15.43 "Transcoder Not Configured"
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Reason: Q.850;cause=127
Content-Length: 0

*Mar 16 08:10:51.082: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:08028800563@41.138.163.34:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKAB0122B
From: "KAY" <sip:015150200@sip.cyberspace.com>;tag=23C66228-1F54
To: <sip:08028800563@41.138.163.34>;tag=1003482543428890
Date: Wed, 16 Mar 2022 08:10:49 GMT
Call-ID: 6C6F334D-A43711EC-A02BC069-6D87FBFC@10.10.15.43
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

*Mar 16 08:10:51.082: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:08028800563@10.10.15.43:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK567c81a717cb6
From: "KAY" <sip:015150200@10.10.15.80>;tag=9887924~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18451251
To: <sip:08028800563@10.10.15.43>;tag=23C669E0-1335
Date: Wed, 16 Mar 2022 09:03:23 GMT
Call-ID: ed7f8500-2311a7db-4313e-500f0a0a@10.10.15.80
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

Counting on your usual support guys

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Wed, 16 Mar 2022 09:24:51 GMT

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

b.winter — Wed, 16 Mar 2022 09:52:47 GMT

Hi,

you receive a "488 Not Acceptable Here" before CUBE sends it's "500 Internal Server Error".

You have to check with the other side where the "488" is coming from (probably from 41.138.163.34), why it is sending it.

Maybe some SIP headers are missing / wrong.

Or because in all the headers, you use private IP's, but you are communicating with a public IP and this public IP doesn't accept calls with private IP's in the SIP headers.

Also, do an upgrade of the router. 15.4.3M3 is really old.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Wed, 16 Mar 2022 10:37:00 GMT

@b.winter thanks for the response the private ip address which is 10.10.15.43 is the voice gateway CUBE and the public ip address 41.138.163.34 is the ITSP. pls see below

CUCM===========VIOCE-GW=======ITSP

10.10.15.80 10.10.15.43 41.138.163.34

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

b.winter — Wed, 16 Mar 2022 10:47:18 GMT

Then you have to check with your ITSP, why they are refusing the call with "488".

There is nothing to do on CUBE, until they tell you what to change.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Wed, 16 Mar 2022 11:00:16 GMT

I have also engage the provider but he keep saying my codec is not correct that i should allow G711ALAW but i can't make the change on the CUCM because other numbers are going and more so if i should try to change the CUCM trunk codec to G711ALAW from the initial G711ULAW all the calls will drop that is why i now make the changes on the dialpeer in the voice gateway and is still not working.

dial-peer voice 403 voip
destination-pattern 08028800563
session protocol sipv2
session target ipv4:41.138.163.34
codec g711alaw
dtmf-relay rtp-nte

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

b.winter — Wed, 16 Mar 2022 11:56:01 GMT

What's the problem, to enable A-law also on the dial-peers towards CUCM?

If all the region / location settings work with u-law, they also should work with a-law (cause it's the same bandwidth).

Only for systems, that don't support a-law (which is in my opinion unlikely), then you need a transcoder somewhere.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

Roger Kallberg — Wed, 16 Mar 2022 15:33:05 GMT

Make these changes on your gateway.

voice class codec 3
 no codec preference 1
 no codec preference 2
 no codec preference 3
 codec preference 1 g711alaw
 codec preference 2 g711ulaw
 codec preference 3 g729r8
! 
dial-peer voice 200 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 300 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 600 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 701 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 400 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 100 voip
 no codec g711ulaw
 voice-class codec 3
!
dial-peer voice 500 voip
 no codec g711ulaw
 voice-class codec 3
!

Apart from this I would recommend you to look over your dial-peer configuration as it is quite messy. Normally you'd need 4 dial-peers, one pair for in- and outbound to/from CM and another pair for in- and outbound to/from your service provider. This could be combined into just two dial-peers, one for CM for both directions and another for the SP in both directions. Personally I'm not a big fan of this, as it makes it harder to see the path or the call and it gives you less flexibility IMHO.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Thu, 17 Mar 2022 14:21:38 GMT

@roger i have tried all that you have suggested but still not working.

Please i still need help

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

Roger Kallberg — Thu, 17 Mar 2022 14:39:10 GMT

Post the output from these debugs running in parallel when making a call in an attached text file.

debug ccsip message
debug voip ccapi inout

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Mon, 21 Mar 2022 09:49:40 GMT

@Roger Kallberg thanks for your response so far and so sorry for my late response attached are the debug you requested for.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

Roger Kallberg — Mon, 21 Mar 2022 11:30:09 GMT

From what I can tell the shared debug does not contain any information for ccsip message. Per the debug shared the call comes in on dial peer 100 and then first uses dial peer 403 outbound, where it disconnects with cause value 47 and then dial peer 401 outbound, where it disconnects with cause value 63. AFAIK the debug does not contain what you initially mentioned, ie there is no error 500 or 488.

Please share the asked for debugs where both of them are running at the same time.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Mon, 21 Mar 2022 12:05:37 GMT

*Mar 21 11:08:08.611: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:08028800563@10.10.15.43:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK58c747cf77be7
From: "KAY" <sip:015150200@10.10.15.80>;tag=10284120~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18462389
To: <sip:08028800563@10.10.15.43>
Date: Mon, 21 Mar 2022 12:00:52 GMT
Call-ID: 8cdcb780-238168f4-43fb4-500f0a0a@10.10.15.80
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Session-ID: 0e990365d0e3eeed8516a4aa10284119;remote=00000000000000000000000000000000
Cisco-Guid: 2363275136-0000065536-0000015091-1343162890
Session-Expires: 1800
P-Asserted-Identity: "KAY" <sip:015150200@10.10.15.80>
Remote-Party-ID: "KAY" <sip:015150200@10.10.15.80>;party=calling;screen=yes;privacy=off
Contact: <sip:015150200@10.10.15.80:5060;transport=tcp>
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 202

v=0
o=CiscoSystemsCCM-SIP 10284120 1 IN IP4 10.10.15.80
s=SIP Call
c=IN IP4 10.10.15.80
t=0 0
m=audio 25770 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Mar 21 11:08:08.619: //293/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK58c747cf77be7
From: "KAY" <sip:015150200@10.10.15.80>;tag=10284120~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18462389
To: <sip:08028800563@10.10.15.43>
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 8cdcb780-238168f4-43fb4-500f0a0a@10.10.15.80
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Content-Length: 0

*Mar 21 11:08:08.623: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08028800563@41.138.163.34:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
Remote-Party-ID: "KAY" <sip:015150200@10.10.15.43>;party=calling;screen=yes;privacy=off
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542
To: <sip:08028800563@41.138.163.34>
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2363275136-0000065536-0000015091-1343162890
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1647860888
Contact: <sip:015150200@10.10.15.43:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 268

v=0
o=CiscoSystemsSIP-GW-UserAgent 2614 4665 IN IP4 10.10.15.43
s=SIP Call
c=IN IP4 10.10.15.43
t=0 0
m=audio 16908 RTP/AVP 0 101 19
c=IN IP4 10.10.15.43
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20

*Mar 21 11:08:08.627: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
To: <sip:08028800563@41.138.163.34>
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542

*Mar 21 11:08:08.831: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
To: <sip:08028800563@41.138.163.34>;tag=1301172986076015
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542

*Mar 21 11:08:08.835: //293/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK58c747cf77be7
From: "KAY" <sip:015150200@10.10.15.80>;tag=10284120~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18462389
To: <sip:08028800563@10.10.15.43>;tag=B49468-7A7
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 8cdcb780-238168f4-43fb4-500f0a0a@10.10.15.80
CSeq: 101 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.15.43 "Transcoder Not Configured"
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Reason: Q.850;cause=63
Content-Length: 0

*Mar 21 11:08:08.835: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:08028800563@41.138.163.34:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542
To: <sip:08028800563@41.138.163.34>;tag=1301172986076015
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

*Mar 21 11:08:08.839: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:08028800563@10.10.15.43:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK58c747cf77be7
From: "KAY" <sip:015150200@10.10.15.80>;tag=10284120~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18462389
To: <sip:08028800563@10.10.15.43>;tag=B49468-7A7
Date: Mon, 21 Mar 2022 12:00:52 GMT
Call-ID: 8cdcb780-238168f4-43fb4-500f0a0a@10.10.15.80
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

Roger Kallberg — Mon, 21 Mar 2022 12:34:40 GMT

The call is sent to your service provider with g711ulaw as the codec.

*Mar 21 11:08:08.623: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:08028800563@41.138.163.34:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
Remote-Party-ID: "KAY" <sip:015150200@10.10.15.43>;party=calling;screen=yes;privacy=off
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542
To: <sip:08028800563@41.138.163.34>
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2363275136-0000065536-0000015091-1343162890
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1647860888
Contact: <sip:015150200@10.10.15.43:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 268

v=0
o=CiscoSystemsSIP-GW-UserAgent 2614 4665 IN IP4 10.10.15.43
s=SIP Call
c=IN IP4 10.10.15.43
t=0 0
m=audio 16908 RTP/AVP 0 101 19
c=IN IP4 10.10.15.43
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20

*Mar 21 11:08:08.627: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
To: <sip:08028800563@41.138.163.34>
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542

*Mar 21 11:08:08.831: //295/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 10.10.15.43:5060;branch=z9hG4bKA91AC7
CSeq: 101 INVITE
Content-Length: 0
Call-ID: 625F1DF-A83E11EC-834A90F9-9731C464@10.10.15.43
To: <sip:08028800563@41.138.163.34>;tag=1301172986076015
From: "KAY" <sip:015150200@10.10.15.43>;tag=B49394-542

*Mar 21 11:08:08.835: //293/8CDCB7800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.10.15.80:5060;branch=z9hG4bK58c747cf77be7
From: "KAY" <sip:015150200@10.10.15.80>;tag=10284120~aa90adaa-cf9d-4579-9e7f-c8715f9da470-18462389
To: <sip:08028800563@10.10.15.43>;tag=B49468-7A7
Date: Mon, 21 Mar 2022 11:08:08 GMT
Call-ID: 8cdcb780-238168f4-43fb4-500f0a0a@10.10.15.80
CSeq: 101 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.15.43 "Transcoder Not Configured"
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Reason: Q.850;cause=63
Content-Length: 0

Then the service provider answers with a 503 Service Unavailable / 500 Internal Server Error and the SBC states Transcoder Not Configured. You'll have to check with the SP why they are doing this and you should check why the call is not using G711 alaw as you'd want it to do.

Re: SENT: SIP/2.0 500 Internal Server Error when calling some numbers

kaysplace — Mon, 21 Mar 2022 13:00:30 GMT

Hi Roger,

Everything is working now after i configured the transcoding and associating it with cube.

Thanks to everyone.