Hi,
I am using osmo-sip-connector 1.20161024 with osmocom-nitb 0.15.1.20161024 on debian jessie. I keep getting the below error[1] causing my syslog to fill up. Also I can see sometimes the sip connector replies with 0.0.0.0 RTP IP address.
Anyone had this issues before ? Any idea what might be causing this?
Regards, Stefan
[1] Oct 25 11:58:28 openbsc1 osmo-sip-connector[283]: length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettport(0x1064c30): zero length packettpor
On 27 Oct 2016, at 14:42, Anonim Stefan fanx07@gmail.com wrote:
Hi,
I am using osmo-sip-connector 1.20161024 with osmocom-nitb 0.15.1.20161024 on debian jessie. I keep getting the below error[1] causing my syslog to fill up. Also I can see sometimes the sip connector replies with 0.0.0.0 RTP IP address.
Anyone had this issues before ? Any idea what might be causing this?
yes, seen it before. Something internal of oRTP... I have seen it triggered by NAT or wrong configuration.. the oRTP code is very "engineered" so it is not easy to follow why it is doing it or how to stop it. :}
holger