Problem with local address rather than the external address in the Via header...
Stewart:
I'm sure that there is a workaround. Are these devices behind the same NAT or different NATs? Can you please describe one failure in detail: which device initiates the call, which side gets audio, etc.
As a quick shot, try setting X_SymmetricRTPEnable.
It's after 1 AM here and I've got to get to bed, but I'll take a look in the morning and try to post a workaround, if the above doesn't help.
slicemaster:
Well, after some relatively unhelpful dialog with Obihai, email correspondence with CallWithUs, and also time and effort in research it would seem this issue is not going to be fixed. Everything I have read about the via field says that for proper implementation of stun the local address in that field needs to be substituted out for the external address discovered via the stun server. Obihai tech support refuses to acknowledge this as a problem, and this is too bad, but at least it’s working for the most part. It’s just sad that a five year old Sipura device does a better job of nat traversal than the top of the line Obihai…
None, the less, all things said and done, I do like my new Obihai.
I just wish the support team would acknowledge the folly and fix it.
Ostracus:
Hmmm, wondering if a local SIP proxy wouldn't work? Say one installed on the router?*
*Assuming your router accepts alternative firmware.
Navigation
[0] Message Index
[*] Previous page