Two Point Foreign Exchange (FX) Telephone Calling (OBI100/OBI110)
NYGuard:
I have read multiple requests for information identical to the request for information (RFI) below, however the request I have read may not be straight forward or ask for additional other call configuration features that are not required with the description below.
I seek to configure two OBI ATA’s, each located at distant geographic locations, in a two-point Foreign Exchange (FX) telephone application where an OBI110 (FXO) connected to POTS dialtone sends / receives calls to/from a telephone connected to an OBI100 (FXS) ATA.
1. Both OBI ATA’s are not located on the same IP Subnet.
2. Incoming POTS calls at the OBI110 Line Port to ring a telephone at one OBI100 ATA.
3. Outgoing calls from the OBI100 to draw dialtone, and place calls via a POTS line connected at the OBI110 ATA.
4. Provisioning for FX service to take place on SP1 on each OBI ATA.
5. Reduce/eliminate the delay time to outbound calling at the end of dialing from the OBI100 on FX calls, if possible.
6. SP2 ports on the OBI100 and OBI110 to remain spare, and available for future SIP provisioning.
7. Maintain Station to Station calling capability between OBI ATA devices via **9 dial access to the OBITALK dial network (**9 + 9D), if possible.
I understand that the above may be redundant on the Forum, however I have not been able to locate a specific example to a solution with what’s indicated above.
Thank you in advance too the major forum contributors for the helpful technical support provided to users on this forum.
drgeoff:
In the following replace 110110110 by the 9 digit OBi number of the OBi110 and replace 100100100 by the 9 digit OBi number of the OBi100.
1a. To make incoming calls on the POTS line of the OBi110 ring both the phone on the OBi110 and the phone on the OBi100 replace the current ph in the 110's LINE port InboundCallRoute with {ph,pp(100100100)}
Or
1b. To make incoming calls on the POTS line of the OBi110 ring only the phone on the OBi100 replace the current ph in the 110's LINE port InboundCallRoute with {pp(100100100)}
2. To make calls dialled on the phone on the OBi100 use the POTS line on the OBi110 you should enable some security. I would use Voice Gateway operation.
On the OBi100 enable Voice Gateway 1. Give it a name eg Rem. Set the AccessNumber to pp(110110110). Set the Digit map to match the numbers you want to dial and exit the OBi110 LINE port. Set and take note of the AuthUserID and the AuthPassword. (You have free choice of both.)
Still on the OBi100 go to the PHONE port OutboundCallRoute and insert immediately before what is already there
{(MRem):vg1},
On the OBi110 go to the Obitalk Service page. For the InboundCallRoute add before what is already there
{100100100>(MLi):Li},
and further down that page for AuthUserID1 and AuthPassword1 enter what you used on the OBi100.
(Note that the above assumes that MLi is configured to match the numbers being dialled on the POTS line.)
NYGuard:
Thanks for the OBI FX config data.
I will implement the config information as provided.
I appreciate the information in your reply.
Regards.
NYGuard:
The following observations were made after all configurations were completed.
Inbound call on the POTS line to the OBI110 via the Line Port to the OBI100 ring and complete OK
Outbound calls placed from the OBI100 towards the OBI110 fails. I reach a recorded message that sounds like an OBITALK message, states: The Number dialed was rejected by the service provider - Reason 403
OBI100 DigitMap is at the DEFAULT (xx.) NOTE: No restrictions on outbound calls
OBI100 Phone Port Primary Line is at the DEFAULT (SP1)
I enabled, and disabled AuthUserID & AuthPassword entries to VG1 at the OBI100, and OBI110 and the one way incoming only operation persists.
Am I supposed to receive a second dial tone before a call attempt is made?
When does the OBI100 spill calling to digits to the OBI110 Line Port to advance a call since the OBITALK Network acts as a Tandem Switch?
I am open to suggestions.
NYG
drgeoff:
1. The configurations for the two directions are completely independent. Nothing for the OBi110 to OBI100 direction impacts on the OBi100 to OBi110 direction and vice versa.
2. If you have local access to either or both the 100 and 110 you should log in to their onboard webservers and look at the Call History. Unfortunately Call History is one of the very few things that are not available via Expert mode on the portal at obitalk.com. What you see in Call History could be very helpful to see where the 100 to 110 is failing.
3. The settings I gave you are based on part of a setup I have with an OBi100 in Japan and an OBi110 in the UK. Mine is slightly different in that the 110 routes calls from the 100 out on SP1 to an Asterisk PBX from whence depending on day of the week and landline or cellular number the call is further routed out on a SIP trunk from the PBX or back to the 110 to the POTS line. My wife uses the facility when she is in Japan to call UK numbers so I know it works though I've haven't yet used it myself so while I am reasonably certain there is no second dial tone I cannot swear to that.
At the 100, the new addition at the beginning of the OutBoundCallRoute should mean that the suitable dialled numbers are sent to Voice Gateway 1, irrespective of the Primary Line setting or anything else later in the OutboundCallRoute.
At the 110 the OBitalk Service page, Inbound Direct Dialing Authentication, AuthMethod should be HTTP Digest (the default).
Check very carefully for inadvertent { ( and , . swaps.
Navigation
[0] Message Index
[#] Next page