CUBE media forking and transcoding

[Gordon Ross]

I'm using CUBE to perform media forking for call recording. Our call recorder can only handle G.711 but calls can come in with other codecs (e.g G.722 or G.729)

I've tried configuring a transcoder on CUBE, but I still get the error:

%VOICE_IEC-3-GW: SIP: Internal Error (200, codec mismatch): IEC=1.1.278.7.106.1.....

Does CUBE actually support transcoding for forked call legs?

Thanks,

Gordon.

[Brandon Buffin]

Are you using CUCM based transcoding or locally registered? Have you tried CUBE LTI?

https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-border-element/115018-configure-cube-lti.html

Brandon

[Gordon Ross]

Yes. This is an exert from my config:

voice class codec 2

 !Inbound codecs
 codec preference 1 g722-64
 codec preference 2 g729r8
 codec preference 3 g711alaw
 video codec h264
!

voice class codec 3

 !Recorder codec
 codec preference 1 g711alaw
 video codec h264

!

dspfarm profile 2 transcode universal  
 codec g729abr8
 codec g729ar8
 codec g711alaw
 codec g729r8
 codec g722-64
 maximum sessions 4
 associate application CUBE

[Brandon Buffin]

Does the profile show active with "show dspfarm profile 2". Can you see the transcoder working with "show dspfarm dsp active" while a call is being attempted?

Brandon

[Gordon Ross]

---

Does the profile show active with "show dspfarm profile 2".

Yes

Dspfarm Profile Configuration

 Profile ID = 2, Service =Universal TRANSCODING, Resource ID = 2  
 Profile Description :  
 Profile Service Mode : Non Secure 
 Profile Admin State : UP 
 Profile Operation State : ACTIVE 
 Application : CUBE   Status : ASSOCIATED 
 Resource Provider : FLEX_DSPRM   Status : UP 
 Total Number of Resources Configured : 4 
 Total Number of Resources Available : 4 
...

---

Can you see the transcoder working with "show dspfarm dsp active" while a call is being attempted?

No.

What debugs can I use to try and see what's going on here?

Gordon.

[Brandon Buffin]

Have you checked the dial peers that are being selected with "debug voip dialpeer"?

[Gordon Ross]

Definitely see it being matched:

002927: Jan 17 14:12:41: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=1198, Peer Info Type=DIALPEER_INFO_SPEECH
002928: Jan 17 14:12:41: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=1198
002929: Jan 17 14:12:41: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
002930: Jan 17 14:12:41: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=1198, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
002931: Jan 17 14:12:41: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0) 
   List of Matched Outgoing Dial-peer(s): 
     1: Dial-peer Tag=4000
002932: Jan 17 14:12:41: %VOICE_IEC-3-GW: SIP: Internal Error (200, codec mismatch): IEC=1.1.278.7.106.1 on callID 41090 GUID=505E1AABFAC711E7A448E8B1242118F3

1198 is the DN assigned in the call recorder and dial-peer 4000 is the one pointing at the call recorder:

dial-peer voice 4000 voip
 description Test Recording System
 destination-pattern 1198
...

[Steven Landon]

debug ccsip messages

will provide some clues on the CODEC negotiation.

[Brandon Buffin]

Do you have the codec configured on this dial peer? Default if not configured is g.729. Also, what inbound dial peer is being matched?

[Gordon Ross]

Outbound to recorder:

voice class codec 3
 codec preference 1 g711alaw
 video codec h264
....
dial-peer voice 4000 voip
 destination-pattern 1198
 session protocol sipv2
 session target ipv4:...
 voice-class codec 3  

Inbound

voice class codec 2
 codec preference 1 g722-64
 codec preference 2 g729r8
 codec preference 3 g711alaw
 video codec h264
....
dial-peer voice 410 voip
 description FROM Jabber Guest VCS
 session protocol sipv2
 session target sip-server
 incoming uri via 2
 voice-class codec 2 offer-all
...

[Steven Landon]

i see your using G711alaw. are you sure your recorder supports alaw and not ulaw?

add ulaw to the transcoder profile. if that is the issue, it should resolve it.

[Gordon Ross]

---

@Steven Landon wrote:

i see your using G711alaw. are you sure your recorder supports alaw and not ulaw?

---

We're in the UK and the recorder is made by a UK company. We both agree that we're using G.711 a-Law here.

Gordon.

[Steven Landon]

can you post some CCSIP logs?

[Gordon Ross]

Attached are some CCSIP debugs. I hope you're better at reading them than me!

Gordon

[Steven Landon]

your VCS is not offering alaw, only ulaw.

a=rtpmap:0 PCMU/8000