Unknown payload type on OpenBSC when using rtp-bridge on LCR
Hi Andreas, After some extensive testing i have done using jolly/rtpmux branch to get rtp to go directly between bsc and softswitch (yate in this case) i came across following scenario. MO call goes to OpenBSC/LCR then to yate routed back to OpenBSC/LCR and MT. Signalling seems all fine including codec negotiating as through out the path AMR/96 is been negotiated well. But once call connected, no rtp stream exist and i see following error on OpenBSC. received RTP frame with unknown payload type 98 Full topology and logs/trace from openbsc, LCR and yate is on this attachment. What could be the reason for bsc to get payload type 98. http://pastebin.com/rPfMamx0 Rgds Nik
On Thu, Mar 15, 2012 at 11:53:26AM +0000, Nik Pakar wrote:
What could be the reason for bsc to get payload type 98.
http://cgit.osmocom.org/cgit/libosmo-abis/tree/include/osmocom/trau/osmo_ort... /*! \brief standard payload type for GSM Full Rate (FR) */ #define RTP_PT_GSM_FULL 3 /*! \brief Osmocom pseudo-static paylaod type for Half Rate (HR) */ #define RTP_PT_GSM_HALF 96 /*! \brief Osmocom pseudo-static paylaod type for Enhanced Full Rate * (EFR) */ #define RTP_PT_GSM_EFR 97 /*! \brief Osmocom pseudo-static paylaod type for Adaptive Multi Rate * (AMR) */ #define RTP_PT_AMR 98 -- - Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
participants (3)
-
Harald Welte -
Nik Pakar -
Peter Stuge