Two Point Foreign Exchange (FX) Telephone Calling (OBI100/OBI110)
NYGuard:
I configured both devices locally after obtaining their individual IP adress, and not through the Obi portal.
I copied your configuration onto a text file, made appropriate modifications where applicable.
Security was enabled, as suggested, and disabled to determine if there is any trouble with peer to peer authentication. I was considering a TRUNK to TRUNK configuration, but I can not locate such information on the web, or it will not yield a functional operation.
I have configured an FX config using Auto Attendant (AA) at the FXO end. I would instead like to install a straight FXO to FXS circuit configuration as if the connection between the OBI110 and OBI100 were a full time DS0 channel.
The end state is to eventually have an inbound connection from a SIP provider to be able to draw dial tone at the FXO without going through AA by first dialing an extension number, the draw second dialtone to advance a call.
The configuration that you described in Japan to UK calling via an IP PBX may be similar to what I want to accomplish. A One Way Dial Repeating Tie Line.
I have been looking at the data logs in the call history of both ATA's. Call data is presented below.
From what I have observed from the data below. The OB110 FXO is not recording FXS call failure events where the OBI100 FXS does. The OBITALK Network appears to be rejecting the Phone Port PRIMARY LINE configuration.
OBI110 call history registers show a call completion event inbound from the OBI110 to the OBI100, OK.
I used different OBI100 PHONE PORT PRIMARY LINE options as a test samples. All call attempts failed.
Number of calls in history: 1 OBI110 (FXO)
Call 1 04/26/2020 20:48:27
Terminal ID LINE1 OBiTALK1
Peer Name
Peer Number 111111111
Direction Inbound Outbound
20:48:27 Ringing
20:48:43 Call Connected
20:48:46 End Call
-----------------------------------------------------------------------
OBI100 with PHONE PORT Primary Line: SP1 (DEFAULT)
Number of calls in history: 2 OBI100 (FXS)
Call 1 04/26/2020 15:46:21
Terminal ID PHONE1 SP1
Peer Name
Peer Number 18005551212 18005551212
Direction Outbound Outbound
15:46:21 New Call
15:46:21 End Call (403 Incorrect Authentication)
Call 2 04/26/2020 15:40:32
Terminal ID PHONE1 SP1
Peer Name
Peer Number1 18005551212 18005551212
Direction Outbound Outbound
15:40:32 New Call
15:40:32 End Call (403 Incorrect Authentication)
-------------------------------------------------------------------------
OBI100 with PHONE PORT Primary Line: OBITALK
Call 1 04/26/2020 17:56:00
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number ob18005551 b18005551 - Dialed number truncated
Direction Outbound Outbound
17:56:00 New Call
17:56:00 End Call (404 Not Found)
Call 2 04/26/2020 17:48:27
Terminal ID OBiTALK1 PHONE1
Peer Name
Peer Number ob180055512 ob18005551
Direction Inbound Inbound
17:48:27 Ringing
17:48:43 Call Connected
17:48:46 End Call
-------------------------------------------------------------------------
OBI100 with PHONE PORT Primary Line: TRUNK GROUP 1
Number of calls in history: 2
OBI100 with PHONE PORT Primary Line: TRUNK GROUP 1
Call 1 04/26/2020 18:12:02
Terminal ID OBiTALK1 PHONE1
Peer Name
Peer Number 222222222
Direction Inbound Inbound
18:12:02 Ringing
18:12:09 Call Connected
18:12:10 End Call
Call 2 04/26/2020 18:07:47
Terminal ID PHONE1 SP1
Peer Name
Peer Number 18005551212 18005551212
Direction Outbound Outbound
18:07:47 New Call
18:07:47 End Call (403 Incorrect Authentication)
The OBITALK network is the middle man in this scenario, and it appears that it does not like what's inbound from the OBI100. Unless there is a remote possibility that the OBI110 is rejecting a connection attempt from OBITALK, and is not registering that even in the call history log.
I have seen similar trouble conditions on ATM networks with switched virtual circuits (SVP) dropping cells one way due to ATM fabric issues. OBITALK is more primitive than ATM, but subject to similar ailments not limited to IP connections.
I believe that what I want to achieve may not be technically possible using the OBI ATA's as configured, and the AUTO ATTENDANT may be the only way possible.
I appreciate your assistance.
NYG
drgeoff:
Apologies. There was an error in the instructions I posted.
MRem was incorrect. There is no map with that name unless one of the User Defined Digit Maps is given that label. No need to do that. Instead, the correct addition to the OBi100 OutboundCallRoute is
{(Mvg1):vg1},
With that change the OBi100's Call History should now show something like
vg1110110110*18005551212
though you may find that the leading v is changed to an underscore.
I have taken my spare OBi110 out of the cupboard and configured it as I instructed above for your OBi100. And I have added the extra part to the in-service 110's OBitalk InBoundCallRoute and added the ID and password. I can successfully dial from a phone on the spare 110 through the in-service 110 and directly (not via SP1 and Asterisk) out on the POTS line to my cell phone. There is no second dial tone.
NYGuard:
Thank you for your follow up.
I will put my equipment puzzle back into operation later today and test the layout, and advise.
Thanks again.
NYG
NYGuard:
drgeoff
I continue to experience outbound call completion trouble. Inbound calls from the POTS Line continue to Test OK.
{(Mvg1):vg1}, replaced all references to MRem, and I included {(Mvg1):vg1}, at the very beginning of the OBI110 InboundCallRoute parameter.
Will the circuit work with Authentication turned off, and if yes, how is it turned it off (Disabled)?
Thanks
drgeoff:
Quote from: NYGuard on April 28, 2020, 01:54:21 pm
and I included {(Mvg1):vg1}, at the very beginning of the OBI110 InboundCallRoute parameter.
Why? I didn't say to change anything on the OBi110.
Navigation
[0] Message Index
[#] Next page
[*] Previous page