Bug #1785
closed
Added by mqng2 over 7 years ago.
Updated over 7 years ago.
Description
I got RTP network error in BTS log starting from commit 8c119f7a0510b75e7fa1b96a37f2a6650e13824f. This leads to no voice at both MS.
The only way to have voice in both MS is to revert this commit.
- Related to Bug #1661: voice not audible in TCH/F-TCH/F calls using osmo-bts-octphy and ortp-0.25 added
Can you please include a reasonable amount of details in the bug report, like:
- what BTS hardware are you using?
- what version of osmo-bts (if any) are you using?
- are you using osmo-bsc or osmo-nitb (if any)?
- which version of ortp has this been observed with?
We basically know nothing about your overall configuration/setup based on your report.
The change explicitly refers to #1661, which refers to ortp-0.25, so it might in the end mean that the order of ortp api calls needs to depend on the specific ortp library version.
I am currenlty in vacation from August 1st to August 8th 2016.
Could be fixed by c77c2a6aa13accbc558888ab788d1148eb9aeb1a but the question remains whether we should support both old and new ortp versions or just bump ortp version requirement and revert c77c2a6aa13accbc558888ab788d1148eb9aeb1a.
Which version of ortp are you using and why?
- % Done changed from 0 to 80
Should be working with a0ff942e927e771875a183c045b3a1676a7d579c
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- Assignee changed from msuraev to laforge
- % Done changed from 80 to 100
No new data from ticket author, works for me with latest master branches so closing for now. Feel free to re-open in case smth is still not working.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
