Guys,
We would like to implement TL MTE with OpenSIPS+RTPProxy for end points registration.
Here is an issue I have found:
- All documentation that is available online showes how to integrate OpenSER(OpenSIPS) with asterisk in realtime, as far as I know TL MTE is not a asterisk in realtime it stores all data in config files.
So the quotations is does any one knows how can we integrate it?
We have faced an issue with NAT traversal and would like to find a the way how to solve this.
IF any one have any other options how to get it done please let me know.
I prepare TL MTE server
I prepare TL MTE server which should go to production in next 2-3 weeks. I want to use openVPN to connect to server - no NATing...
Peter
Hello, We have successfully
Hello,
We have successfully got TL MTE with OpenSIPS and RTPProxy. It took awhile to get everything to NAT Properly... We only have 1 open issues which involves inbound caller id.
We have the CLI working with inbound calls that support rPort and Polycom phones not using 3.2.x.
However, and standard SIP device that registers shows the proper NAME, however the number shows
"MyExt-MyTenant". On the Polycom Phones using newer software this appears once the call is placed on hold.
Any thoughts?
How is OpenVPN working?
Hey Had,
How is your OpenVPN solution working? Any gotcha's that have come up?
We've been testing the Yealink phones with the OpenVPN client built in and I'd have to say it's pretty amazing. It takes a bit a messing around to get all the keys straight and get the tar file loaded on the phone... but once it's done, it just works. I've tested them behind every cheap router I could find... Linksys, D-Link, etc. all have passed the test so far.
I guess ring groups and paging groups come to mind as maybe causing issues? I'm also wondering how many endpoints you are up to on the MTE? Does the OpenVPN server scale well enough? Do you use individual keys for each phone? tenant? or do you just share one?
Any info would be appreciated.
Thanks,
rf
use siproxd at client site, dont try to fight nat on the public internet, that isnt where the problem exists.
send me your email and I can send you more documentation.