| Obi 202 cannot dial out.. I have a new 202 set up with virtualpbx and for the life of me I cannot get it to dial out...I know my creds are good because it will register and I can accept inbound calls. It rings, I have voice, etc. When I attempt to dial out, all I get is the 404 or 484 server rejection error that the OBI puts out. Any ideas? I have tried different dial plans and nothing works... |
|
 VexorgTR
join:2012-08-27
Sheffield Lake, OH | I think we'll need to know your service provider, to help further. |
|
|
|
| Virtualpbx.com |
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | Does Virtualpbx actually provide an outbound service or do they just provide the PBX functionality?
Do you know for sure that you have outbound routes configured? |
|
| They provide the outbound service. I have the outbound proxy set up with their specs as provided to me. Also have a dial plan they gave me. |
|
 XCOMdigitalnUllPremium
join:2002-06-10
Spring, TX
 ·flowroute
 ·Comcast
·voip.ms
·Callcentric
·SIPBRI
| ouch!
A few threads down there is a post regarding this company and their reviews and it seems to be an awful company.
Good luck!
Edit:
I see it was directed to you as well... Again Good Luck.
--
[nUll@dcypher ~]$ |
|
| reply to dirt_diver
Does your Call History show connections to the SP for VirtualPBX?
With the OBi you have to route to the Service Provider, as well as have a dial map.
Routing can be done by default, or by dialing the routing code. |
|
| The call history in the Obi shows 404 and 484 errors based on the number I call, either a 7 digit local or 1 plus area code. VPBX shows nothing on their end. I am not familiar with the routing code. They are not being cooperative in providing me anything but the most basic SIP settings as user/pass, proxy (in/out), dns settings, NAT map and keep alive. The obi will take inbound calls so I know my reg is good. Frustrating... |
|
| In the OBi's Call History, does it show the correct SPx in the right hand pane for Terminal ID? If not, you need to change OutboundCallRoute for the Phone port in question, dial a prefix to select VPBX, or change Primary Line to select VPBX by default.
Otherwise, if you get 484 (Address Incomplete) on 7-digit dialing, VPBX doesn't accept that format. Try 11- or 10-digit dialing, or ask them what dialing formats they accept. The Peer Number in the right hand pane of Call History should show what the OBi actually sent to VPBX.
|
|
| Yeah, it shows the correct SP in the pane and there are no prefixes to dial. Their system sets the area code so you can do 7 digit dialing. I have tried all dialing combinations. Thanks for the suggestion though. The funny thing is is that I can set it up on Voip.ms and make calls in the time it takes to type this..I know its an outbound config thing, surely... |
|
| Do you have another ATA, IP phone, softphone or smartphone app that is working with VPBX? If so, compare the SIP headers and try to make the OBi's look the same. If not, have them do a trace -- your router or ISP may be somehow corrupting the request. Pay particular attention to the domain names (or IP addresses) in the URI and in the From and To headers.
To easily capture SIP packets from the OBi, set Device Admin->Syslog->Server to the local IP address of your PC, and SPx Service->X_SipDebugOption to Log All Messages. Capture with Wireshark or a syslog server. |
|
| reply to dirt_diver
Line 1 of Call History shows who called (Phone or Inc.Line), followed by the Outgoing Service Provider selected.
Line 3 (Peer Number) shows what you dialed, followed by what was sent to the SP. What are you sending to VPBX?
OBi uses **x codes to directly route calls to specific Service Providers, such as SP1, SP2, the Auto Attendant, or the Line.
There is only one default SP route with the default dial plan. |
|
| Call Ended (404 Not Found)
or
Call Ended (Address Incomplete)
based on dialing 7 or 11 digit, this is what I get. If that is what you are asking. |
|
| reply to Stewart
I will download wireshark and give it a whirl. Thanks. |
|
