All my voip street DIDs were reporting unreachable. So, I checked in Asterisk CLI and neither my SIP or IAX trunks are registering with VoIPStreet. I cannot even get on their web site to see what is going on. Anyone else having problems?
 
Anyone having problems with VoIPStreet?
Submitted by hcrane on Wed, 07/30/2008 - 5:37pm.
same thing here
Wed, 07/30/2008 - 5:59pm
I am having the same trouble
 
It is back up
Wed, 07/30/2008 - 8:04pm
This brings up an issue for me...What would happen if one day a SIP trunk provider decided th just turn off the lights and go home for good? Does anyone know how one would get their DIDs over to another provider quickly?
 
It's happened several times,
Wed, 07/30/2008 - 8:21pm
It's happened several times, and now just with Voip providers.
One of the most dramatic was PacWest. Google for the nitty gritty
--
Scott
aka "Skyking"
 
registration problems are back again
Tue, 08/19/2008 - 1:36pm
Last Thur and Fri I was having problems with registration on voipstreet, again, again.
Vitelity works great for my San Diego customers but is a bit spotty out of SF for some reason.
Anyone have suggestions for another provider? Teliax perhaps? I can't stay with voipstreet.
Btw, to answer the "what happens if they go out of business". the strategy I've taken is to always get a telco (att/verizon) or cable phone number and use that as the primary inbound number terminated to a card in the PBX. Then I pay the telco to forward on busy to a local voip DID. If I have too many problems, then I change the forwarding. The voip DID number is never published so I'm not bound to any provider.
thx, michael
 
Multiple forward sessions
Tue, 08/19/2008 - 5:54pm
Quote:
then I change the forwarding. The voip DID number is never published so I'm not bound to any provider
Most telcos will not forward more than one session on Busy Forward. If you have a different experience please let us know (and the name of the *LEC).
--
Scott
aka "Skyking"
 
AT&T (BellSouth)
Tue, 08/19/2008 - 7:23pm
Scott,
I have three numbers owned by organizations that CAN'T loose the numbers so we have them Remote Call Forwarded to SIP DIDs that never get published. In normal operation the talk number has three talk paths to the SIP lead with has twelve channels. The other two have dual talk paths. During disasters and other events I have done a change through AT&T to move the number of talk paths to 12 on the primary number and 24 on the SIP Trunks with that carrier.
The cost is about 18.00/Talk Path for the RCF function in GA. Hopefully AT&T will always be there :-) Or at least always under some name..
---------------
 
Learn something new every day
Tue, 08/19/2008 - 8:27pm
Phonebuff -
That's good info, I have tried to order additional forward paths and never got any traction.
I should have dug into the tarriff.
By any miracle do you have the USOC for that feature? It should be valid in any former Bell operating company.
--
Scott
aka "Skyking"
 
Yes,
I have a USOC guide
Fri, 08/22/2008 - 2:06pm
Yes,
I have a USOC guide book here somewhere..
The Miracle is I can find it in this mess I call an office --
New York Telephone 11/1987 So not sure it will have the MultiPath Call Forward ---
http://wholesale.att.com/products_and_services/local/resale/call_...
-------------------------
 
Member Since:
2006-06-01