Modify SDP header in CUBE for RTP media attribute

[Simon Coventry]

Hello All,

I need to modify the RTP payload type from '96' to '101' on my 200 OK response message to provider. 

I have tried to implement the below SIP profile for this but I seem to be missing something......

request ANY sdp-header Audio-Attribute modify "a=fmtp:96 0-15" "a=fmtp:101 0-15"

Any Suggestions Welcome?

SIP MSG

SIP/2.0 200 OK
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK208A01712
From: <sip:anonymous@anonymous.invalid>;tag=2E6F7A49-1AD5
To: <sip:7400@XXX.XXX.XXX.XXX>;tag=19045284~0a6255a7-7c70-4c94-af23-3ac6c791818a-40998895
Date: Mon, 10 Apr 2017 11:59:39 GMT
Call-ID: 46BDDB8A-1D1B11E7-A261902B-C652E21D@XXX.XXX.XXX.XXX
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Supported: replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
P-Asserted-Identity: "Caller Name" <sip:8012@XXX.XXX.XXX.XXX>
Remote-Party-ID: "Caller Name" <sip:8012@XXX.XXX.XXX.XXX>;party=called;screen=yes;privacy=off
Contact: <sip:7400@XXX.XXX.XXX.XXX:5060>
Content-Type: application/sdp
Content-Length: 240

v=0
o=CiscoSystemsCCM-SIP 19045284 1 IN IP4 XXX.XXX.XXX.XXX
s=SIP Call
c=IN IP4 XXX.XXX.XXX.XXX
b=TIAS:64000
b=AS:64
t=0 0
m=audio 27224 RTP/AVP 0 96
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15

[Ayodeji Okanlawon]

Hi,

You dont need to use sip profiles to change the payload type for rtp nte.

You can easily configure this on the dial-peer facing your ITSP

conf t

dial-peer voice xx voip

rtp payload-type nte 101

NB: This should be the default, perhaps someone in your team has changed this previously to 96

[Simon Coventry]

Hi,

Thanks for the suggestion but this is a message sent in response to an INVITE. Telco negotiates RTP payload type 96 for DTMF whereas I want to force type 101 in my response.

[Ayodeji Okanlawon]

If Telco is negotiating 96, you cant force 101. They are sending you 96 because that's what they want to do. You can try and use early offer and send 101 to your Telco and see if that will change what they send in their 200 OK to you. Either way with newer IOS CUBE can easily interwork between different dynamic payloads

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-dymc-payld-dtmf.html

on your dial-peer

  voice-class sip asymmetric payload full