anomaly0617
Member
- Joined
- Feb 9, 2012
- Messages
- 50
- Reaction score
- 11
Hi all,
We have SIP trunks through Vitelity connected to a PBX-in-a-Flash server. I'm not sure that the version is germaine, other than to say that it's a fairly recent load. The server itself is probably only a year old.
We're running into a problem when our ISP decides to do maintenance, a backhoe decides to eat the line somewhere along the last mile, a drunk driver decides to have his car make out with a phone pole, or some similar happenstance where we lose internet connectivity for a few hours. When the internet comes back up, all services in our server room come back except for my SIP trunks to Vitelity. If people call the number, they get a busy signal, and I get an email that looks like this:
The only way to resolve the issue seems to be to reboot the PBX, which disrupts internal communications between offices and creates angry bosses. So, I'd like a better way. Is there a way to monitor the SIP trunk status and the connectivity to inbound[whatever].vitelity.net and kick off a script to just reset the SIP trunks when the connectivity is restored?
I'm fairly bash-script knowledgeable, so I can likely write the above script to check for connectivity. Mostly I just need the command(s) to reset the SIP trunks.
We have SIP trunks through Vitelity connected to a PBX-in-a-Flash server. I'm not sure that the version is germaine, other than to say that it's a fairly recent load. The server itself is probably only a year old.
We're running into a problem when our ISP decides to do maintenance, a backhoe decides to eat the line somewhere along the last mile, a drunk driver decides to have his car make out with a phone pole, or some similar happenstance where we lose internet connectivity for a few hours. When the internet comes back up, all services in our server room come back except for my SIP trunks to Vitelity. If people call the number, they get a busy signal, and I get an email that looks like this:
-----Original Message-----
From: Vitelity [mailto:[email protected]]
Sent: {Day}, {Date} {Time}
To: {me}
Subject: Vitelity Failed Call Notification for {DID}
Dear Customer,
A call to your DID {DID} from {CallerID} has failed at {Time} on {Date}. We received 'CHANUNAVAIL' when attempting to route the call to your server or device. This number is configured to route to the peer none.
This error usually means your server or device is not currently registered to our servers. Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page.
If you are aware of this error and are purposely having calls fail to utilize our failover feature, please disregard this message.
If you no longer wish to receive these emails, you may disable this feature within the My Account section of the customer user portal.
Sincerely,
Vitelity Communications
[email protected]
The only way to resolve the issue seems to be to reboot the PBX, which disrupts internal communications between offices and creates angry bosses. So, I'd like a better way. Is there a way to monitor the SIP trunk status and the connectivity to inbound[whatever].vitelity.net and kick off a script to just reset the SIP trunks when the connectivity is restored?
I'm fairly bash-script knowledgeable, so I can likely write the above script to check for connectivity. Mostly I just need the command(s) to reset the SIP trunks.