FOOD FOR THOUGHT Inbound Vitelity DID issue

[geopeterwc]

I have several accounts with Vitelity and several DIDs on each of those accounts. The Vitelity services have worked reliably for several years. My DIDs are configured to use ChanSIP (I know, I know ... need to convert to PJSIP). Several DIDs are active on the same VPS server at CrownCloud, and until very recently this has not been an issue. But Vitelity has apparently (recently?) implemented a security feature that blocks the IP address of the CrownCloud VPS if there are "too many simultaneous registration attempts" resulting in blocking all registrations for the DIDs assigned to the iPBX2027-D services.

Vitelity tech support says the IP address block is is due to the DIDs simultaneously requesting registration, and recommend changing the registration frequency of each of the DIDs to get around their automatic block of the IP address for the server due to the multiple registration attempts. The GUI setting in Asterisk SIP Settings for ChanSIP reflects registration expiry of 3600 seconds ... but I don't see a way to adjusting that on a per-DID basis?

Is this a ChanSIP issue? If the configuration of the DIDs are changed to PJSIP, is the registration problem resolved?

 

[chris_c_]

Try this, and post back to let us know if it worked for you:

In your Chan_SIP Trunk settings (under the Registration String field), you can manually set the expiry for each DID. Instead of letting them all default to 3600, vary them slightly:

DID 1: user:[email protected]/ext~600
DID 2: user:[email protected]/ext~660
DID 3: user:[email protected]/ext~720

 

[geopeterwc]

Thanks, Chris ...

But, I'm not clear on the structure of the registration string. I get the userID, password and domain portion of the recommendation, but not clear on the last portion that begins with [/EMAIL] and what follows, the "/ext~600" represent?

This is a typical registration string for DIDs that are to register to the Vitelity inbound35.vitelity.net registration server:
subacct4:[email protected]:5060/6502221234
subacct5:[email protected]:5060/6502224321
(where the string following the "/" is the DID number.

How would you format the registration string to ensure variable registration times? And, what does the number following the "~" represent ... seconds?

 

[geopeterwc]

I've reduced the number of DIDs on this iPBX 2027-D to three priority DIDs before making any changes to the registration string on them. I'm reluctant to re-enable the full inventory of DIDs until I am confident that the revised registration string works properly.

 

[chris_c_]

The number after the tilde is the Expiry Timer, in seconds. I'd suggest staggering these like 300, 310, 320, 330, etc. Or, 3600, 3630, 3660, 3690...

subacct4:[email protected]:5060/6502221234~300
subacct5:[email protected]:5060/6502224321~310

After you update these strings and "Apply Config," you can verify the timers are active by running sip show registry from the Asterisk CLI, or sudo asterisk -rx "sip show registry" from the linux terminal. You should see the "Refresh" column showing different countdown values for each line.

 

[geopeterwc]

I applied the suggested change to the registration string to two DIDs. This is the result:
Host dnsmgr Username Refresh State Reg.Time
inbound35.vitelity.net:5060 Y pf94_0003 105 Registered Thu, 07 May 2026 14:14:25
inbound35.vitelity.net:5060 Y pf94_0004 105 Registered Thu, 07 May 2026 14:14:25

I used 300 and 600 for the time - but the Refresh column shows the same (105) for both. Not sure that this change in the registration string affected anything!

 

[kenn10]

Its been a while since I got rid of Vitelity, but it was never necessary to put the DID number and an associated extension or registration timer. You simply register a trunk on whichever sub-accounts and the DID's are delivered to the PBX as you direct them from the Vitelity site.. You use incoming routes to route the DID's in the PBX. I don't know how many sub-accounts you are dealing with but I don't understand why Vitelity would be limiting the number of registrations.

If that isn't the way it works anymore, then I'd recommend you boot Vitelity and check out BulkVS or another carrier.

 

[kenn10]

@geopeterwc are you keeping separate trunks for billing purposes for your clients? I don't understand your setup if they are all on the same PBX system since you cannot have separate partitions for each client.

For PJSIP, you might want to study this thread for a good How To I wrote when I still had Vitelity.

SOLVED Thread 'Vitelity PJSIP HOW-TO'

Nov 28, 2020

Does any one have Vitelity set up for PJSIP? do I need to setup one for outgoing and incoming using PJSIP?
I Need some guidance. Was looking for some screen shot setups.

Thanks

• Hometech
• Replies: 15
• Forum: Trunks & Providers

 

[geopeterwc]

I'd recommend you boot Vitelity and check out BulkVS or another carrier

Thanks for the suggestion, Ken. Is BulkVS your preferred/recommendation? I've ben thinking about making a switch but hadn't identified an alternative.

My use of Vitelity dates way back from the time that I started getting into VoIP services and (I think) Vitelity was the recommended provider. Mostly, I use the services for demonstration and private/home use. My client list is very limited and they're on their own servers - so it makes billing and managing the systems for them mostly a non-issue.

I have studied the discussion thread you provided some time ago, but it seemed that every time I started to get into the process something (mostly personal) got in the way. And then, until the current fiasco, the services with Vitelity related to the registration issue. So, it is probably time to change!

Your insight and expertise has been my go-to for a long time! Thanks!

 

[chris_c_]

I second a switch to BulkVS, it's generally significantly cheaper than Vitelity, making it a better option for dirt-cheap VoIP calls.

 

[kenn10]

Bulkvs has been rock solid for me. At $0.16/DID per month, its a darned good deal. They do provide caller-id on inbound calls for a very tiny fee and you cannot opt out of it but it is minimal compared to what you pay with Vitelity. Also, they provide E911 service very cheaply. Another good thing about Bulkvs is that you can set up a secondary server for inbound calls to try if the primary is unresponsive. You can set up individual systems and trunks to those systems (I have 6 different systems including my main home cloud server and a test server that is also my backup if the primary goes down.

I just found Vitelity too restrictive and less than helpful after they got bought out. Keep in mind that Bulkvs only handles calls to the US and Canada so if you need international calling, check out Anveo-Direct for inexpensive termination of international outbound calls.

 

[dghundt]

Bulkvs has been rock solid for me. At $0.16/DID per month, its a darned good deal. They do provide caller-id on inbound calls for a very tiny fee and you cannot opt out of it but it is minimal compared to what you pay with Vitelity. Also, they provide E911 service very cheaply. Another good thing about Bulkvs is that you can set up a secondary server for inbound calls to try if the primary is unresponsive. You can set up individual systems and trunks to those systems (I have 6 different systems including my main home cloud server and a test server that is also my backup if the primary goes down.

I just found Vitelity too restrictive and less than helpful after they got bought out. Keep in mind that Bulkvs only handles calls to the US and Canada so if you need international calling, check out Anveo-Direct for inexpensive termination of international outbound calls.

Is there a Bulkvs inbound per minute charge, or a minimum spend per month?

I have one of the old Vitelity Ward Specials with four channel inbound, no per minute usage fees. It is my Precious.

 

[chris_c_]

Is there a Bulkvs inbound per minute charge, or a minimum spend per month?

I have one of the old Vitelity Ward Specials with four channel inbound, no per minute usage fees. It is my Precious.

That's a great deal, definitely keep it. On BulkVS, inbound voice calls are generally billed at $0.0003 per minute, CNAM lookup is $0.002 per query for each inbound call, and DID phone number costs start around $0.06 per month.