voip.ms sip trunk

[Leon Zetekoff]

would be nice to have a template for voip.ms. While I have it working with generic I don't like seeing a RED marking under trunks

thanks leon

 

[N_G]

We are working on it together with Voip.MS

 

[Andyshawn]

Nick, that good news. I've been using voip.ms for a few years now and have no issues with call quality.
I'd really like to see the red go away also, so looking forward to the template.

 

[Leon Zetekoff]

Good deal Nick...any idea when it will be available? Shouldnt take that long?

THanks leon

 

[N_G]

The process is in Voip.MS hands and has been for several weeks. If you are a good customer of them give them a call and tell them to get cracking on the interop...

 

[Leon Zetekoff]

Mon, Jun 4 2018 9:40am - William Lopez Hello Leon,

This is still a work in progress, I'm afraid I don't have any further information to provide at the moment. I do apologize for the inconvenience.

__
William Lopez
VoIP.ms Customer Service

 

[Leon Zetekoff]

Looks like nothing has been done ---

Hello Leon,

I got an update from management however it is basically the same information we have provided, there is still some paperwork and other details we need to work on with 3cx before we can get this ready. At this time there is no ETA, but rest assured we are doing our best to have this ready asap.

__
Alex Lopez
VoIP.ms Customer Servic

 

[TechieM2]

I'm waiting on this as well.

My generic trunk is green and shows registered on 3CX and VoIP.ms, but I can't send outgoing calls through it (haven't tested incoming recently).
I get: Call or Registration to externalnumber@([email protected]) has failed.
I filed a support ticket this morning and their reply indicated the 10000 should be my account number, so it seems 3CX isn't forming that line properly when making the call out.

Leon: Did you have to do anything special to get yours working for now while we wait for an official template?

 

[PAPBX]

We have been using VoIP.ms since 3CX V9 with no issues. It works with registration and fixed IP address.

 

[leejor]

I get: Call or Registration to externalnumber@([email protected]) has failed.
I filed a support ticket this morning and their reply indicated the 10000 should be my account number, so it seems 3CX isn't forming that line properly when making the call out.

Could it be that 10000 is your 3CX trunk number, and it has been put into a field that it should not have been?

 

[Leon Zetekoff]

I believe the 10000 is the trunk number. I am currently using it with IP Auth. I had that same issue with the 10000 being sent as the userid

 

[Leon Zetekoff]

@nick any update on this?they said (see above) something about paperwork is holdup. Also, the tutorial on a website they sent me is for an older version and told them it needs to be updated to 15.5

 

[NickD_3CX]

Not the Nick you expected, but a Nick nonetheless...

Nothing yet, so same status as before.

 

[DFPet]

Add Me to the list of people who use Voip.MS and want to connect it to 3CX.
Decision will be soon (CallCentric is probably our default selection).

 

[mobilityproject]

I managed to setup inbound and outbound calls with Voip.ms. Work fine but I don't know how to get inbound Caller ID working. I just get the number but no CNAM. Anyone have this working? Is it a matter of editing the 'Source Pattern' / 'Replace Pattern' in the SIP Trunk setup?

 

[NickD_3CX]

Do you have the CNAM lookup enabled in the VoIP.MS portal? I believe it is a paid service their offer and is not enabled by default.
Then you would probably have to change the "CallerName" value to "From : Display Name" in the Inbound Parameters tab...

 

[DFPet]

I have been trying to get VOIP.MS working with our Cloud based 3CX setup.

I keep getting 403 rejections even though I have verified accounts and passwords.

Please confirm that this should work with the cloud based version of 3CX.

Do I need to so something with SEC_IGNORE_USER_AGENT?

 

[bigdessert]

We use VOIP.MS as trunks for all our installs and do not have to change SEC_IGNORE_USER_AGENT parameter. There was a patch I think back in the early 15 version that caused that but not there anymore.

 

[DFPet]

Thank you, bigdessert - I will continue to try - but I would feel more comfortable if I knew VOIP.MS was working on the cloud based version. Do you have it working there?

 

[bigdessert]

We run both cloud and on-prem. We do not however run PBXexpress. We run all cloud instances on our own debian installations in the cloud. The only changes we need to do are make sure you put in the did and under inbound parameters change "CallerName" from From:User Part to From Display Name to get caller ID working.