Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

dynamic rtp payload type 123

Hello,

We have a problem about dynamic rtp payload type 123. Wireshark is shown rtp packets which dynamic rtp payload type is 123 malformed.

why do cisco gateways send dynamic rtp payload type 123 packets to non-cisco gateways? Can we disable dynamic rtp payload type 123 nagotiation?

please help,

Thanks

Omer

Everyone's tags (5)
7 REPLIES

dynamic rtp payload type 123

What is your hardware?

Do you have already see this doc?

Enable RTP Signaling on AS5350 and AS5400

In order to prevent errors caused by RTP packets of payload type “123” on Cisco AS5350 and AS5400 series platforms, RTP signal processing is disabled by default. Under some circumstances, packets of this type can cause an invalid memory address error in AS5350 and AS5400 series platforms, potentially crashing the devices.

On these models, you can enable RTP signal processing using the voice-fastpath voice-rtp-signalling enable hidden configuration command. However, before you enable RTP signal processing, prepare the platform to handle RTP packets of payload type “123” by enabling T-CCS.

After you prepare the platform, you can use these commands in order to enable or disable RTP signal processing.

  • In order to enable RTP signal processing, use this command:

    Router(config)#voice-fastpath voice-rtp-signalling enable
    
  • In order to disable RTP signal processing, use this command:
    Router(config)#no voice-fastpath voice-rtp-signalling enable
New Member

dynamic rtp payload type 123

Hello,

thank you for your answer, i read it and also we configured before. the problem is non-cisco media gateways are caused some problems reported by one service provider we work together.Is there any way to disable it?

sh run | i voice-fa

no voice-fastpath enable

Cisco IOS Software, 5400 Software (C5400-JK9SU2_IVS-M), Version 12.4(22)T4, RELEASE SOFTWARE (fc2)

ROM: System Bootstrap, Version 12.4(22r)T, RELEASE SOFTWARE (fc1)

Cisco AS5400XM (BCM) processor (revision 0x22) with 393215K/131072K bytes of memory.

Processor board ID JAE14520L7Z

SB-1 CPU at 750MHz, Implementation 1025, Rev 0.3, 256KB L2 Cache

Last reset from power-on

Manufacture Cookie Info:

EEPROM Version 0x4, Board ID 0x4BD,

Board Hardware Version 2.7, Item Number 800-6572037-05,

Board Revision B0, Serial Number JAE14520L7Z.

Processor 0x0, MAC Address 0022.bddb.58c0

2 Gigabit Ethernet interfaces

512 Serial interfaces

16 Channelized/Clear E1/PRI ports

60 DSPs, 960 Voice resources

512K bytes of NVRAM.

126976K bytes of ATA External CompactFlash (Read/Write)

thanks

dynamic rtp payload type 123

If I understand, is the other party that send you a message with payload 123.

Correct?

If your AS5400 is controlled via mgcp try the command no mgcp rtp payload type ...

If your AS5400 uses SIP try

voice service voip

sip

asymmetric payload {dtmf | dynamic-codecs | full | system}

I


New Member

dynamic rtp payload type 123

No, Our media Gateways send their softswitch with payload 123. They don't want to take this malformed packets which is rtp payload type 123. i don't know why the cisco gws send these packets.

Regards

Re: dynamic rtp payload type 123

what is the signalling protocol used? SIP?

Can you add the output of debug ccsip messages?

Can you add the config of your AS?

Regards.

New Member

Re: dynamic rtp payload type 123

Hello again,

Signaling Protocol is H323. I can not take debug h323 etc  logs because of the device has too many calls. But you can find below rtp debug that i took before.

I can not share AS full config because privacy stuff.

!

voice service voip

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw

h323

  emptycapability

  h225 timeout setup 10

modem passthrough nse codec g711ulaw

sip

  bind control source-interface Loopback3

  bind media source-interface Loopback3

!

!

!

no voice-fastpath enable

!        

!

dial-peer voice 1 voip

description INCOMING Traffic

service incomingcallcontrol

voice-class aaa 3

voice-class codec 101

incoming called-number B00290..........$

dtmf-relay rtp-nte h245-signal h245-alphanumeric

fax-relay ecm disable

fax rate 14400

ip qos dscp cs3 signaling

no vad

!

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs tx s=10.10.10.1(23690), d=172.20.60.2(12994), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

RTP(54397): fs rx s=10.10.11.1(20928), d=10.10.10.1(23946), pt=123, ts=1303D47D, ssrc=20351C0, marker=0

Regards

Re: dynamic rtp payload type 123

I don't understand who is the first to offert payload 123. Can you add a wireshark trace?

Do you have already try to change the cisco CAS RTP payload 123 to a different value?

e.g. under dial-peer use rtp payload-type cisco-cas-payload 105

Regards.

1743
Views
0
Helpful
7
Replies
CreatePlease login to create content