cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1555
Views
0
Helpful
8
Replies

Transcoder not being invoked

Good Day,

 

We are currently having an issue whereby Transcoders registered to CUCM via SCCP are not being invoked, when we register them to the CUBE then it works. Transcoders are registered to CUCM and are in the correct groups which is assigned to the devices and the device pool.

 

Certain calls are failing and the debug ccsip message from the CUBE is "Transcoder Not Configured".

Any help will be appreciated. TIA.

 

Call Flow

CUCM->CUBE->ITSP

 

dspfarm profile 1 transcode
codec g729abr8
codec g729ar8
codec g711alaw
codec g711ulaw
codec g729r8
codec g729br8
maximum sessions 8
associate application SCCP

 

CUCM Version - 10.5.2.14900-16

CUBE/DSP IOS(4451) - isr4400- universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin 

8 Replies 8

CUCM Version - 10.5.2.14900-16

CUBE/DSP IOS(4451) - isr4400- universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin 

Anthony Holloway
Cisco Employee
Cisco Employee
You didn't give enough information to fully understand your problem.

When you say "...register them to the CUBE..." are you talking about Local Transcoding Interface (LTI) on CUBE?

Is it possible you can show your CUBE SIP messages during a failed call?

Hi Anthony,

 

Thanks for the response, when I say register them to the CUBE, I mean the below configuration invokes the transcoder.

 

dspfarm profile 1 transcode
codec g729abr8
codec g729ar8
codec g711alaw
codec g711ulaw
codec g729br8
codec g729r8
maximum sessions 2
associate application CUBE
!

 

Unfortunately I cannot send the actual debug due to company policy, but here is the call flow of the failed call.

 

Basically whats happening is the external number is requesting g711a, which I do have in my regions but the call is still failing no matter how much I have tried to fix it, on the cube message you will see transcoder not available. So its trying to be invoked but its failing.

 

 

 

Yes, that's called LTI.

Can you share the output of "show dspfarm profile 1"

Since you shared a sanitized version of the 503, could you share a sanitized version of the CUBE to ITSP early offer INVITE with SDP, and then the ITSP to CUBE response 200 OK with SDP?

I'm thinking two things:

1) You are offering ulaw to the ITSP and they are responding with alaw, thus CUBE needs to fix the codecs, but...

2) You do not have your transcoder successfully registered yet

Do you have the mode border element command under voice service voip, and if so, has the router be reloaded since that command was put in place?

Hi Anthony,

 

Please see below

 

***CUBE TO ITSP***

289236: Nov 4 07:31:31.383: //5516466/5A1001000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:011XXXXXXX@ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP CUBE:5060;branch=z9hG4bK1B304A10
From: <sip:012XXXXXX@CUBE>;tag=30E85B56-CE6
To: <sip:011XXXXXXX@ITSP>
Date: Mon, 04 Nov 2019 07:31:31 GMT
Call-ID: 3118AB7E-FDFB11E9-A85EB711-1E4D17F0@197.100.27.177
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1510998272-0000065536-0000009145-0385164810
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S4b
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1572845491
Contact: <sip:012XXXXXXX@CUBE:5060>
Expires: 180
Allow-Events: kpml, telephone-event
Max-Forwards: 68
P-Asserted-Identity: <sip:012XXXXXX@CUBE>
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 300
v=0
o=CiscoSystemsSIP-GW-UserAgent 5453 4701 IN IP4 197.100.27.177
s=SIP Call
c=IN IP4 X.X.X.X
t=0 0
m=audio 40978 RTP/AVP 18 8 101
c=IN IP4 X.X.X.X
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20


Timestamp: 3655697491383
UTC Timestamp:3655697491383
Source Filename: rbt95D9.tmp

 

***200 OK***

289238: Nov 4 07:31:31.642: //5516466/5A1001000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP CUBE:5060;branch=z9hG4bK1B304A10
From: <sip:012XXXXXX@CUBE>;tag=30E85B56-CE6
To: <sip:011XXXXXX@ITSP>;tag=fw+SHSrnPVT9dYBj.i
Call-ID: 3118AB7E-FDFB11E9-A85EB711-1E4D17F0@197.100.27.177
CSeq: 101 INVITE
Timestamp: 1572845491
Contact: <sip:27XXXXXXX@ITSP:5060;transport=udp>
Allow: INVITE, ACK, BYE, CANCEL, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS, UPDATE
Content-Type: application/sdp
Server: PortaSIP
Content-Length: 190

v=0
o=PortaSIP 1898468815 1 IN IP4 172.16.254.14
s=-
t=0 0
m=audio 20176 RTP/AVP 8 101
c=IN IP4 1ITSP
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

ZATPTARTRPUX001#show dspfarm profile 1
Dspfarm Profile Configuration

Profile ID = 1, Service = TRANSCODING, Resource ID = 1
Profile Description :
Profile Service Mode : Non Secure
Profile Admin State : UP
Profile Operation State : ACTIVE
Application : SCCP Status : ASSOCIATED
Resource Provider : FLEX_DSPRM Status : UP
Total Number of Resources Configured : 8
Total Number of Resources Available : 8
Total Number of Resources Out of Service : 0
Total Number of Resources Active : 0
Codec Configuration: num_of_codecs:6
Codec : g729br8, Maximum Packetization Period : 60
Codec : g729r8, Maximum Packetization Period : 60
Codec : g711ulaw, Maximum Packetization Period : 30
Codec : g711alaw, Maximum Packetization Period : 30
Codec : g729ar8, Maximum Packetization Period : 60
Codec : g729abr8, Maximum Packetization Period : 60
ZATPTARTRPUX001#

 

 

voice service voip
mode border-element
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
registrar server expires max 28000 min 60
asserted-id pai
midcall-signaling passthru media-change
early-offer forced
!
voice class codec 2
codec preference 1 g711alaw
!
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711alaw
!

 

 

 

 

What codecs do you specify in the dial peers (a) for the CUBE/ITSP leg and (b) CUBE/CUCM leg?

I'm thinking that LTI vs CUCM registered transcoders deal with different scenarios as LTI is invoked by the CUBE, whereas CUCM registered resources are invoked by CUCM when the call offered by the CUBE doesn't match CUCM settings for the destination.

 

Hello Jarry,

Did you find a solution to this? I am facing the same issue

 

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: