Obi 110 bridging to Obi100 passing through to a PAP2
Dale:
Some progress:
calls to the work number at home ring at home and on the PAP2 at the cabin. Good.
Calls to the cabin ring on PH. Good.
So the bridging and VG5 seem to be working.
I cannot dial anything from the PAP2 though. I get dial tone and any number I dial results in busy signal.
(Even for OB commands such as **0)
PAP2 (I am using Line 2) is set as follows:
SIP Port: 5063
Proxy: 192.168.1.131:5060 (Cabin Obi box and port, also tried without the port number)
Register: No
User id: PAP2
Dial plan: ([x*][x*].)
Enable ip dialling: no (also tried yes)
Cabin SP1 X_InboundCallRoute: {pap2>([1-9]x?*@@.):pp},{pap2>(<911:12073243644>):sp2},{pap2>**0:aa},{pap2>***:aa2},{pap2>(<**1:>(Msp1)):sp1},{pap2>(<**2:>(Msp2)):sp2},{pap2>(<**9:>(Mpp)):pp},{pap2>(<2*>(Msp1)):pp},{pap2>0:ph},{pap2:}
Any suggestions on what I should try next?
RonR:
Is the PAP2 set to?:
Make Call Without Reg: Yes
IP Dialing is not required.
Dale:
yes make and ans calls without registration are both set to YES on the PAP2.
Dale:
are attempts to dial out from the PAP2 regarded as inbound calls on the Obi?
If so how would the the name 'pap2' get associated with the pap2 rules in the inbound call route of SP1 on the obi? Does it assume that because there is a 'PAP2' VG5 pointing to the PAP2 device that incoming dial attempts from that IP address are from the same device?
RonR:
When you make a call from the PAP2, the PAP2 sends the call to its Proxy Server (192.168.1.131:5060) which is the OBi100. Port 5060 is SP1. The PAP2's UserID (pap2) becomes the incoming CallerID, which is matched in SP1's X_InboundCallRoute rules. These rules also match the called number pattern to decide where to route the call. For example, the {pap2>**0:aa} rule sends calls from the pap2 dialed as **0 to the Auto Attendant.
VG5 is used to send calls from the OBi100 to the PAP2.
SP1 status should be: Registration Not Required
Navigation
[0] Message Index
[#] Next page
[*] Previous page