We are currently using the MTE version with one tenant currently.
There are a few extensions that we have set as host=ip address to route the calls to another switch/device.
This switch/device will takes care of the registrations for those phones.
When a user dials *86 to check voicemail, the call is forwarded to the Thirdlane without any issues. However when we add another tenant and a trunk with a different dns host resolving to the same IP as the switch/device as the first tenant the calls from the 2nd tenant extensions get a username mismatch error.
For example:
Tenant 1 - blue.switch.com (200.200.200.201)
Extension 500 -> host=blue.switch.com
Trunk -> blue.switch.com
Tenant 2 - red.switch.com
Extension 500 -> host=red.switch.com (200.200.200.201)
Trunk -> red.switch.com
When ext 500 from blue tenant calls in to check voicemail it functions no problem.
However when the ext 500 from red calls it sends it to the blue context and then the username mismatch occurs.
We would like to have all our tenants register to the external switch yet have them routed to the Thirdlane for voicemail and other functions.
There must be a way to
There must be a way to determine the extension the call needs to go to as well as refer to the from header within SIP. I can manipulate the headers going to Thirdlane to route the calls to the appropriate extensions' application.
For example:
If ext 500 from red.com wants to check his voicemail, we would want to send the call to MTE to red-500 voicemail application.
which is why you need to
which is why you need to stop trunking based on ip and start using sip authentication.
you will never get this to work. If you are trusting based on IP _ONLY_; its going to match just 1 trunk, usually the first one it comes to in the config. How do you suppose its going to just 'know' its red.switch.com instead of blue.switch.com? All asterisk see's is a sip packet coming in from that given IP. Thats the whole reason for auth names and secret. There is no PFM setting or a res_crystalball module in play. If you want to parse multiple registrations and contexts from a single ip, you MUST use authentication.