# RTP Payload type of 35 **URL:** \ **Category:** Integration\ **Created:** [January 18, 2021, 11:52pm UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285 "2021-01-18T23:52:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![laduma-adamc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/laduma-adamc/32/764_2.png) [@laduma-adamc](https://mediasoup.discourse.group/u/laduma-adamc)\ **Post date:** [January 18, 2021, 11:52pm UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/1 "2021-01-18T23:52:44Z")
One of the libraries that we are potentially using to send RTP packets to a plain transport using raw h264 only sends the the RTP headers with a payload type of 35. I know looking through the documentation on the `RtpCodecCapability` that it states that the router dynamically assigns the preferredPayloadType if it is not set, and that it will be in the range of 96-127. Is there a way of allowing the media soup router to pass the RTP packets to a producer with a codec of payload type 35? I’m fully expecting the answer to be know, but I thought I would ask. Thank you for a great tool. Adam ---
**Author:** ![nazar-pc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/nazar-pc/32/369_2.png) [@nazar-pc](https://mediasoup.discourse.group/u/nazar-pc)\ **Post date:** [January 19, 2021, 1:42am UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/2 "2021-01-19T01:42:17Z")
35 is not common, but I don’t see why it wouldn’t work. It is just a number. ---
**Author:** ![laduma-adamc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/laduma-adamc/32/764_2.png) [@laduma-adamc](https://mediasoup.discourse.group/u/laduma-adamc)\ **Post date:** [January 19, 2021, 9:20am UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/3 "2021-01-19T09:20:43Z")
A payload type of 35 is undefined in the RTP spec, and I know that media soup tries to adhere to the spec as close as possible. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [January 19, 2021, 9:44am UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/4 "2021-01-19T09:44:44Z")
Hace you actually tried it? ---
**Author:** ![laduma-adamc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/laduma-adamc/32/764_2.png) [@laduma-adamc](https://mediasoup.discourse.group/u/laduma-adamc)\ **Post date:** [January 19, 2021, 11:26am UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/5 "2021-01-19T11:26:09Z")
Yes, I’ve set the `preferredPayloadType` to 35 in the router codec configuration, and I constantly get this error message in the logs with every UDP packet received : `mediasoup:WARN:Channel [pid:49] RTC::Transport::ReceiveRtpPacket() | no suitable Producer for received RTP packet [ssrc:1642420806, payloadType:35]` ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [January 19, 2021, 12:55pm UTC](https://mediasoup.discourse.group/t/rtp-payload-type-of-35/2285/6 "2021-01-19T12:55:28Z")
Well, please check the documentation. The sender can send whatever payload type number, no need for it to match the value in the media codecs given to the Router. > [@laduma-adamc](#): > > mediasoup:WARN:Channel [pid:49] RTC::Transport::ReceiveRtpPacket() | no suitable Producer for received RTP packet [ssrc:1642420806, payloadType:35] So the `rtpParameters` you gave to `transport.produce()` are wrong (at least regarding the codec payload type).