iPhone 10 with voip.ms branded softphone, registers, can make calls but busy signal caling app

Help & Support
1

Hi, decade long user of voip.ms. I’ve setup many softphones but this one has me stumped. An iPhone 10 running voip.ms branded (Acrobit) softphone. On the web interface, the sub-account registers (green) and can make outgoing calls and calls to 4443. However, when dialing the DID, immediately goes to busy signal. However, on the app, the “voip".ms” logo remains white, not green. Logo turns red if I change to TCP.

Have tried both UDP and TCP, no difference, left setting at UDP. Have verified softphone and settings in voip.ms are using the same server. vancouver3.voip.ms

Have tested on second device, Samsung Galaxy FE7 tablet, same result, sub-account registers in the web interface (green) but the “voip.ms” label on the softphone screen is white.

Any clues to what I’m missing? This particular phone in question is using the voip.ms branded softphone. Other devices are using the paid Acrobits softphone and Groundwire.

Thanks.

2

Hi,

What routing did you set for your DID, is it the subaccount you use with your softphone?

Have you registered your softphone on the EXACT same server that your POP is set to for your DID?

3

Hi, Thanks for the response. Yes, softphone and DID are using the same server, vancouver3.voip.ms

Strangely, after about 12 hours, without any further changes, the softphone can now receive calls. The voip.ms logo remains white though instead of green. However, on other devices we have the paid Acrobits apps (Softphone or Groundwire) and the logo is green when connected to the servers.

So suddenly, the setup started working. Could it be just bad luck that I setup the softphone on a new device when there was an outage?

4

The color of the logo may be a feature of the app. VoIP.ms is using a striped down version of the Acrobit app, maybe the color of the logo is one think that was removed in the VoIP.ms version.

As for the call routing, many things are possible. Maybe it was an outage. Maybe is was a weird registration issue too.

If you are using your subaccount with more than one devices, it may also have been a SIP forking issue.

I am glad it works for you!

5

I have the app set for UDP and it has worked flawlessly for me.

6

Thanks IntPlus for the commments.

At one point, Zoiper was installed too at the same time for some period of the testing so that may have contributed to some of the issues.Adage is, one sip client active at any one time to eliminate factors.

7

Thanks NYTelephone. Same here, I have UDP enabled on other sip apps and it works fine.

1 Like