I saw your reference to this thread over on Whirlpool . Please accept my apology for not responding sooner.
We have spent the last couple of months re-engineering our core platform to address this very question.
You are 100% right, alot of things must be in place (some we don't have control over) before Voxalot decides to UNPROXY the RTP. The solution we have been working on allows the user to explicitly decided whether or not they want Voxalot to proxy (with the default being "Yes").
Under the new platform, if the user sets this value to "No" Voxalot will do 2 things:
1. It will disable the RTPProxy for the user and
2. Voxalot will initiated the RE_INVITEs rather than relying on the end points to do so.
The good news is the telephony piece is built and currently in test and the user interface that drives these new settings is currently being developed as part of our web-site re-design.
If you are interested v164, we are more than happy to give you access to this new telephony engine to perform your own analysis.
Thanks.
__________________
Martin
Please post support questions on the forum. Do not send PMs unless requested.
|