Question,
Think this is more asterisk but related heavily to using asterisk in a MTE.
I have multiple trunks setup on one proxy for outgoing calls for each tenant and one trunk setup for inbound for all tenants. Sounds about right. Problem is Asterisk doesn't match the inbound trunk correctly and assigns inbound calls to what I initially thought was the last registration but it actually looks as if it's the last entry in SIP.conf as I only have one registration on this box.
This shouldn't be an issue but earlier on it broke my incoming calls for all tenants as I added a tenant and the trunk I added for that tenant didn't have the correct settings (insecure etc.) to allow calls so Asterisk was just rejecting them. Is there a workaround for this or do I need to keep moving the trunk to the bottom of sip.conf? I was advised by you guys that I was doing the correct thing to have one trunk for incoming.
Please Advise!
TIA.
Brian
Hi Erik, Thanks for the
Hi Erik,
Thanks for the response. At the moment it's setup like this for billing purposes.
Brian
then you may need a new
then you may need a new billing system. Is it billing off the proxies log or asterisk cdr? How is the sip proxy even going to differentiate your customers if its trusting purely on ip?
I think you misunderstand.
I think you misunderstand. It's billing by subscriber. Are you familiar with that concept?
Erik, Erik, you misunderstood
Erik,
Erik, you misunderstood my initial post, apologies for lack of clarification.
Each 'outbound' trunk uses Authentication user & secret. Each one unique to each MTE client. In come cases they may have more than one. The 'inbound' trunk is the only one that is a registration. My issue is that Asterisk likes to ignore this and will from time to time assign the inbound call to one of the 'outbound' trunks.
It seems to be a known bug/limitation of the Asterisk SIP stack. We break down the billing at proxy level by subscriber. This allows us to do things like rate the calls in realtime and we also do prepay billing which is subscriber based. We generate rated CDR's in realtime based on the subscriber calling.
Our main business is SIP trunking, I'm not going to start making the proxy treat MTE customers differently.
We essentially treat each MTE user as a seperate PBX which is the way tenants on a MTE asterisk PBX should be treated.
Brian
if you are not using proxy authentication in sip (ie user/secret) then you can have only ONE trunk per IP. How is ANY system supposed to know which trunk to use when the only identification you have to differentiate them is an ip address? Why do you feel you need more than one trunk per asterisk machine to the same provider?