SOLVED IncrediblePBX16-15 stopped being able to make outgoing calls

[kameleon]

One of my PBXs just stopped being able to make outbound calls today. Yesterday was fine. I am using Skyetel for outbound and Voip.ms for inbound. Skyetel sees the outbound call in the logs but it never rings on the other end. Watching the logs it just cycles through all the various skyetel trunks finally ending in a "Retransmission timeout reached on transmission..........." error. I have restored the vm from a backup from 2 days ago just to see if it was something that changed last night or today but that did nothing, same errors. Nothing I can see has changed on my end. Where can I start to dig in and see what is going on here?


****EDIT**** Seems I have it working by adding the outbound CID to all the individual Skyetel trunks, which has never had a CID set before only on the outbound route. Disregard.

 

[stanjohn]

Could be time to review our CID as I just received the new rules on CIDs from voipms, hope to see more providers moving in this direction.

/quote on/
Dear Stanley,

In case you missed it, we would like to remind you that due to the recent rulings in favor of protecting and empowering consumers, on January 1st 2020, we will start enforcing valid Caller IDs as per the NANPA and ITU-T E.164 standards. This regulation will apply for all customers including reseller’s clients.
Considering that VoIP.ms already has call filtering solutions, enforcing Caller IDs is simply the cherry on the cake! In fact, we found value in joining all the other phone providers in this massive industry shift in order to ensure that consumers benefit from a minimum level of protection against nuisance calls.
Therefore, calls displaying the following Caller ID information will be blocked by our platform:

1. International calls with Caller ID containing less than 7 digits and greater than 15 digits;
2. North America calls with Caller ID not containing exactly 10 digits (exception will be made for 7 digits for 310-xxx numbers);
3. North America calls with Caller ID containing 10 digits, but with an unassigned NPA (first 3 digits of the number);
4. North America calls with Caller ID containing 10 digits, but where an unassignable NXX is used (i.e. the second block of 3 digits where the first digit is either zero (0) or one (1)).
5. Compliance with these standards will ensure proper call termination and reduce potential connection issues, thus resulting in a great call completion rate.

If you are passing your Caller ID from VoIP.ms customer portal, please review your Caller ID number to make sure it complies with these standards. In order to do so, head over to your portal, click “Main Menu”, “Account Settings”, then the “General” tab, edit the “Caller ID number” field and hit save. You can also do this for your Sub Accounts by going to "Sub Accounts" menu, then click on "Manage Sub Accounts".
If you are passing your Caller ID from your own system such as a PBX or a switch, you only need to make sure it follows the guidelines aforementioned.
On top of this, the good news is that we have a few features in our roadmap to allow you to add an extra layer of protection against nuisance calls.
/quote off/

 

[dallas]

I've been wanting to do this to filter incoming call to my IncrediblePBX for some time but haven't been able to achive it.