This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Nik Pakar nikpakar at gmail.comHi 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120315/62bdaa5c/attachment.htm>