Hi there,
Currently I use Vitelity for my DIDs and services which I started about a month ago. Over Easter I had an interesting change and was curious if others have experienced such occurances with other providers.
When I signed up for an account I received HOST information as follows:
HOST=inbound7.vitelity.net
This worked well for about one month. Then over Easter my family and friends emailed that they couldn't reach me all day. I then received an email from Vitelity stating the following:
We received 'CHANUNAVAIL' when attempting to route the call to your server or device.
This error usually means your server or device is not currently registered to our servers.
Well, I checked my trunk settings and compared them to Vitelity's support info for my account. I noticed that the HOST information had changed to .
HOST=inbound6.vitelity.net
I thought wow! They can change the host information without notification and my phone would be dead in the water.
I am not sure how to solve this problem or prevent this from happening again. Is this common that HOST would be changed?
Thanks,
Jim
Currently I use Vitelity for my DIDs and services which I started about a month ago. Over Easter I had an interesting change and was curious if others have experienced such occurances with other providers.
When I signed up for an account I received HOST information as follows:
HOST=inbound7.vitelity.net
This worked well for about one month. Then over Easter my family and friends emailed that they couldn't reach me all day. I then received an email from Vitelity stating the following:
We received 'CHANUNAVAIL' when attempting to route the call to your server or device.
This error usually means your server or device is not currently registered to our servers.
Well, I checked my trunk settings and compared them to Vitelity's support info for my account. I noticed that the HOST information had changed to .
HOST=inbound6.vitelity.net
I thought wow! They can change the host information without notification and my phone would be dead in the water.
I am not sure how to solve this problem or prevent this from happening again. Is this common that HOST would be changed?
Thanks,
Jim

