First off, I do appreciate the responses.
@SkykinOH - I do know that the Bandwidth.com infrastructure is what SIPStation uses. In fact, this was a part of why I chose to use SIPStation. Having used Bandwidth.com SIP trunking in the past & being aware of their venerable position & service, I was comfortable of the idea of using SIPStation, knowing that it was “really” kind of reselling Bandwidth.com’s SIP trunking, and simply excluding the phone-based support, etc.
More recently I was speaking with a Bandwidth.com rep & he said that although SIPStation uses Bandwidth.com’s infrastructure & the contract for service actually seems to be directly with Bandwidth.com, it is NOT actually the same SIP trunking service, and it is NOT using the same Bandwidth.com infrastructure/equipment that Bandwidth.com’s native SIP trunking service does. He made specific reference to the fact that SIPStation does SIP registration to authenticate our SIP endpoint & establish the IP calls need sent to, whereas Bandwidth.com does not use SIP registration & instead requires a static IP address on our side, which they setup as the SIP endpoint on their end. Having used Bandwidth.com’s SIP trunking in my company a few years ago, I remembered this & realized that he was probably right, at least to the extent that the SIP trunk is setup differently. On the other hand, it is clear to see that the SIP trunks setup for SIPStation are pointing the SIP endpoints trunk1.phonebooth.net & trunk2.phonebooth.net. Phonebooth being the hosted PBX service from Bandwidth.com, it would seem that these are actually the same SIP trunk endpoints that Bandwidth.com uses for their Phonebooth hosted PBX service. But the Bandwidth.com sales guy gave me the impression otherwise. He also specifically stated that the Bandwidth.com SIP trunking service has more redundancy built-in & more geographic locations from which they can send calls into us, and used the static IP address requirement & lack of SIP registration being required to support this assertion.
So I am a bit unclear as to who is correct here. Maybe everyone is & there is more to the story/picture.
@Philippe - Again, thank you very much for the response. Receiving a response usually makes a tremendous difference to me. There is nothing more frustrating than having a service down that is completely out of your (my) control & feeling that you are speaking into a black hole as your only channel of support for resolution. So THANK YOU!
Aside from that,
-
It seems that someone edited my 2nd post/reply & somehow the last sentence got added to my reply rather than yours or Scott’s.
-
So if you don’t see any sign of problem with the infrastructure/logging, etc. maybe it was a transient issue with Level3 or other upstream ISP that Bandwidth.com uses…?
Regarding the service in general:
3. I have been trying to determine the best way to financially directly support the FreePBX project, as we use it to create solutions for our small business customers & we certainly don’t want it to go anywhere. I felt like the SIPStation SIP trunking service was valuable & something I could trust as being more or less equivalent to direct from Bandwidth.com. This ptrunkingresented to me an excellent way to start pushing some kind of (although currently pretty minor) financial support toward the FreePBX project (I’m sure you guys don’t make too much on these individual trunks, but something is better than nothing, so if I can do something, then I will). It was easy for me to justify using SIPStation for these reasons, as the SIP service itself is a necessity of course.
-
Regarding moving from SIPStation to Bandwidth.com, one of my clients on SIPStation is currently paying CenturyLink over $18/mo to maintain a market expansion line & their toll free #. SIPStation doesn’t support toll free, so they are paying CL to forward the toll free to the market expansion line & the market expansion line to the company’s main DID which is currently in SIPStation’s system. If you guys supported having a toll-free number on their account, they could drop that $18/mo service from CL & save some money. Bandwidth.com does support having a toll-free #, and I think it is $6-8/mo. Bandwidth.com is also willing to negotiate pricing in such a way that it seems like the customer will be winning on both ends by switching to them. Add that 24x7 support & it just seems like a good move. Add to that the fact that they’ll set me up as a referral partner & I get a commission too & it again strengthens their position.
-
Truthfully if you guys just had a feature in the SIPStation web interface that enabled us to forward their DID to someone’s cell phone, this would have even been a major issue. Still inconvenient, but definitely workable. I know the SIPStation FAQ has said this is coming & you guys are working hard on it, but I think it has said that for nearly a year. Has anyone really been working on it?
-
Sorry that I made such a big fuss this morning in the first place. I was seeing the situation as both of these customers having absolutely NO phone service ALL DAY today & that would have been a very big problem for them & me as their I.T. & phone guy. However, it seemed that the issue only lasted until around 10:45-11am Mountain Time. Still having now phones for 2-3 hours in the morning is not great for these customers, but it’s a lot better than the worst-case scenario that I thought I was looking at.
Also, if it helps in troubleshooting or figuring out what the problem was, I found out that their phones would actually ring on inbound calls, but after answering, there was NO audio for either party. So it seems like RTP media wasn’t making it through either way. I was also told that outbound calls would be silent & then just hang up. I’m not sure whether those actually rang through to the called party.
Thanks.