Voip.ms - delayed inbound issue with DID 5

See my answers below;

Not sure if it's caused by Voip.ms or the Bcm50.
I used that same account on a Cisco ATA for 5 years without any issue but since it's on the Bcm50 i have that issue where i need to make an outside call to wake up the SIP trunks in order to be able to receive inbound calls.

How are you calling from the softphone? out on another type of trunk or other? I tried copper line,SIP line and Cellular with the same results.
-Did you see the status of registration in SIP Trunks/Accounts? I allways shows "Registered" with montreal7.voip.ms
-Also do the alarms show any 51104 alarms? No alarms at all

Any taker?

The most likely cause is your router's implementation of NAT. After some period of time, the router closes the NAT session that it created for the communication between the BCM and VoIP.ms. With the session closed, packets from VoIP.ms cannot reach the BCM. When you make an outbound call, a packet to VoIP.ms opens a session and incoming calls work for a while again.

You have two options:
1. Configure the BCM to send keep alive messages to VoIP.ms
2. Configure port forwarding on your router to direct all packets received on the BCM's SIP port (usually 5060) to the BCM's IP address

An issue I suddenly had with calling certain numbers and getting nothing but 'dead air' might be related.

I've had my Flowroute SIP trunks for 5+ years, and they've worked well during that time. Suddenly a couple of months ago I couldn't call my brother in the Reno area. I'd dial his number and get 'dead air.'

I contacted Flowroute and they told me my BCM50 was sending the local LAN IP address instead of the public IP address. Due to some sort of compensation Flowroute told me they could usually still route the calls correctly. I thought this was weird as I'd had minimal issues with my SIP trunks during those 5+ years.

The Flowroute tech suggested I enable NAT traversal on my trunks. All I saw in the SIP settings under the advanced tab was a check box for NAT compensation, so I went ahead and enabled this in my BCM50. The system also made me enable media relay before I could enable NAT compensation.

After I made the above changes I made a test call to my brother and it went through. I had Flowroute look at their logs for the test call and they told me my BCM50 was now sending the public IP address as it should. I shrugged my shoulders and have left it that way ever since.

I've attached a screenshot of my current settings.

Brian Cox
Georgia Telephone

Also at voip.ms under account settings you have:
A: Asterisk, IP PBX, Gateway or VoIP Switch
B: ATA Device, IP Phone or Softphone

Which one is yours set too? I have mine at ATA
I will test mine vigorously when time but a couple stars deserved.




=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

In Voip.ms config i have it set for IP PBX because it would not work under ATA.
As exsmogger suggest i will try the "NAT compensation" and report back.
Also like ucxguy keepalive option so will try it if the first suggestion doesn't work.

My issue appears to be fixed.

No inbound after little awhile, unless I kick start it with making an outbound call....much like gbergers issue.
For me the account on the BCM showed registered but showed unregistered at voip.ms portal
Playing with some settings also kick started....or made it worse.

I noticed in exsmogger's screen shot he has ITSP association method set to: From header proxy address match.
Even though Wiki Voip.ms with BCM states "From header domain match" I thought I would try it anyway and that is what fixed my issue.

My settings for Voip.ms are attached in the link below in PDF format.

Thanks for the tip guys.









=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

i have it set for IP PBX because it would not work under ATA."

I actually had it set to that too, but in testing the other day it was left at ATA, it only works once for me then the portal shows it as deregistered right after the test call, so I put it back to PBX today.



=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

Curlycord,

A knowledgeable Flowroute tech told me the correct ITSP association method for their service was From header proxy address match a couple of years ago. This seems to be a setting many of the SIP providers don't advertise.

Brian Cox
Georgia Telephone

Good tip indeed, thanks!



=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

**FIXED**

Enabling "NAT compensation and Media Relay" didn't fix it so i forwarded port 5060 to the Bcm50 Ip adress and it works like a charm!
ucxguy have a star!

You'll probably notice hackers banging away at port 5060 since it's now open. I've seen all my SIP channels in use when I've opened port 5060 in the past.

Brian Cox
Georgia Telephone

I agree, try to avoid that.
Try the one that fixed it for me, but disable that port forward on 5060 first.
And/Or you should always disable any SIP ALG settings on the router, the hinder, not help.



=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

I noticed that after an hour all 12 SIP trunks were in use showing "alerting" in Bcm Monitor...

I fixed it by allowing only incoming connection from VoipMS on port 5060, no more issue to report.

Did you try the other fixes?
-disable any SIP ALG
-use: From header proxy address match

If we do not have 5060 forwarded then you shouldn't either.



=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN

I disabled SIP ALG and used: "From header proxy address match" but it's a no go, not sure why but by allowing only VoipMS requests on port 5060 works so i guess i will leave it like that for now.

Thanks for your help curlycord!

If your router can filter by IP address you should be OK as it will block requests from any other IP address. I wish my router had that feature.

Brian Cox
Georgia Telephone

Yes it does, Asus RT-AC1900P that i got used for $100.00,i really like Asus routers.