Multi Tenant registrations issue with VOIP.MS

[Chidado]

Has anyone had issues with gateway registrations using voip.ms? Using Fusion, we can only setup/register each gateway once with eachof voip.ms POP server. Since they only have approx 9 North American POP servers ie; montreal5.voip.ms, montreal6.voip.ms etc, we can only register one domain per pop server.
Any thoughts/suggestions? We have used another provider, and we didn't have this issue. we could register all of them to one server. Keeping each domain separate gateway.

*note* once the gateway is registered to each Voip.MS POP server, we have no issues inbound-outbound. Just running out of POP,s to register with. If you try to register 2 domains to the same sever pop (montrel5.voip.ms) they both get the boot

 

[DigitalDaz]

I would say this is a question you should be asking voip.ms, looks like its an issue they need to resolve.

 

[Chidado]

Thank you DDaz. I have chatted with them this a.m. They're not so clear on our platform, since they are more accustomed to single devices. Not big on the multi tenant.
Question: Can we have a single gateway, but populated for ALL the domains? Not a gateway for each domain?
If we add individual gateways, with the same credentials, of course, it fails. Too many registrations under the same login. How about one for the entire Fusion. Is that feasible?

 

[ad5ou]

In the Gateway settings, click "advanced" to see all options and select "Global" as the domain.

 

[Chidado]

@ad5ou
If thats all it is, then I love you and Fusion. Both. And DDaz. I will do that and update.

 

[DigitalDaz]

Yes you can have a gateway for all clients as @ad5ou has said.

 

[Chidado]

Hey Gentlemen. It worked well for the outgoing -all using the single trunk- credentials. Incoming not so well. Investigating...

 

[ad5ou]

Inbound would depend on how voipms is setup. When I still had numbers as voipms, I used "SIP URI" option for their DID destination.
You could set a single URI for your server or a URI for each customer.
sip:1{DID}@pbx.domain.com:5080 for example.
Then the fusion side would be expecting 11 digit phone number on whichever domain has the number.

 

[Chidado]

@ad5ou :: That's exactly where I was going to look. I didnt know where to look~! I know that its an incoming direction issue. VOIPms is sending the call and since fusion is multi-tenant, it needs to know where or which domain to deliver it to. I will try your info and post back. Appreciate your advice.

 

[ad5ou]

Unless you want the customer specific info at voipms, you can use a single URI for all numbers like I posted above.
In Fusion, put the correct numbers under the correct domains and all will be well.

The domain part of the incoming URI doesn't matter to freeswitch/fusion. Once Fusion finds a match in the database it routes to the proper dial plan.

 

[Chidado]

Going to give this another shot after hours. I have added all the SIP URI. I will post results. I have a good feeling this will work.
Thank you.

 

[Chidado]

@ad5ou
Just applied the SIP URI and they flew into the proper domains. Credit to you Sir. Thank you for the directions.

 

[DigitalDaz]

So this is solved now?

 

[Chidado]

Solved and working well.