-
Re: Busy Signal Outgoing Calls
99% of my clients are using Comcast. SIP7 worked great until I had to move them to SIP due to the SIP7 outage. Now on SIP I get busy signals consistently. Putting a ticket in doesn't help when I have a tech onsite. My customers ask why do I have to wait for support from our carrier, why can't you call someone while the tech is onsite. I have setup a syslog server and receive debugging information but being on the outside looking in I cannot fix any of the issues. There is no one I can call to work on the problems when I need to work on them. I wish I could afford to sit and wait for a reply to my tickets but in reality I have to move on to the next task just like Voipo.
Greenlantern even if we had support for our own domains it is still a process to figure out the issue, find the corrective action, then implement the changes. I shouldn't have to wait for my clients to complain, then try to figure out the exact call so I can get the Call Reference ID, and that's assuming the call completed and is listed in the call history, create a ticket, wait for a response, hope my client is available to see if the fix worked, then report back.
I have been working on a solution to monitor my clients so that I can anticipate issues and implement corrective measures before my clients even know there is a problem. So far 99% of the issues we experience the corrective action has to be done at the carrier level just like this issue with compact sip headers. And since the issues are at the carrier level for me to monitor and implement corrective actions I would thus have to become a company like Voipo, which is not in my scope.
Ok I'm done venting
Joe Siepka
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks