Two Point Foreign Exchange (FX) Telephone Calling (OBI100/OBI110)
NYGuard:
Condition resolved.
The update provided to insert {(Mvg1):vg1}, at the OBI-110 was my misunderstanding. After rereading the text it became obvious that a OBI110 was used at the closed end of the FX circuit, and configured as an FXS.
I though I was faced with an authentication trouble, and or other something else with the Config of the equipment. That is why I wanted to turn off Authentication to remove one possible stumbling block, and pursuit the trouble.
I managed to locate one option configuration that resulted in outbound call failure. The trouble was isolated at the OBITALK SERVICE SETTINGS InboundCallRoute configuration.
The information originally provided indicated that in the OBI110 Obitalk Service Setting InboundCallRoute, the following was to be placed in front of what was there. The Inbound Call Route window displayed: ph.
The value in the InboundCallRoute setting was it's default. I reset all equipment to Factory default prior to any re-provisioning.
At the OBITALK SERVICE SETTINGS, I observed the following: InboundCallRoute = ph
Change #1: I inserted {2000xxxxx>(MLi):Li}, in front of the value found in the InboundCallRoute window to read: {2000xxxxx>(MLi):Li},ph
The above resulted in a ring no answer condition on call attempts at the OBI100. I was more than likely ringing the phone port on the OBI110.
I removed the ph in a quick test. This resulted in fast busy conditions AKA: Reorder Tone, on outbound calls.
Change #2: I replaced the InboundCallRoute "ph" with "Li" to now read: {2000xxxxx>(MLi):Li},Li
After change #2, all outbound, and inbound calls at the OBI100 completed OK to/from a second POTS line.
OBI110 Software Build: 1.3.0 (Build: 2886), Hardware Ver: 2.8
OBI100 Software Build: 1.3.0 (Build: 2886), Hardware Ver: 3.4
I will assume that FX Line configuration options would apply to a OBI200/202 to OBI212 equipment layout. Unless software/hardware versions with newer equipment require different configuration values.
Thank you for your patience & assistance.
NYG
drgeoff:
Quote from: NYGuard on April 28, 2020, 07:25:15 pm
Change #2: I replaced the InboundCallRoute "ph" with "Li" to now read: {2000xxxxx>(MLi):Li},Li
1. Without a ph the OBi110 will be unable to receive calls to its phone using the Obitalk service. You originally posted that you would like to retain the **9 possibility.
{2000xxxxx>(MLi):Li},{ph}
will allow any OBi to call the OBi110's phone by dialling **9 followed by the 9 digit number of your 110. Or
{2000xxxx>(Mli):Li},{2000xxxx:ph}
will limit it to calls from your OBi100.
2. These methods work with any OBi ATA or OBiPhone released to date. (Provided not using an ancient firmware or a firmware/configuration that has been adversely customised.)
3. The Bible for all this stuff is the Admin Guide. https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf for the ATA. Page 130 for Voice Gateways and page 191 onwards for Call Routeing and Digit Maps.
4. When you fully understand Call Routeing and Digit maps you will be able to make optimisations such as minimising post-dial delays and short cuts. For example, adding your version of
<0:**9110110110>
into the OBi100 Phone port Digit Map gives the option of calling the OBi110 phone by simply dialling a single 0.
NYGuard:
Thank again.
Good information, however {ph} was not the default option in the InboundCallRoute field, ph was, and as stated, call completion could not take place until Li was added after the argument string.
If there were a named config settings that enables OBITALK ***9 station to station calling in addition to POTS stage one dial access, I can not identify it the original instructions.
A procedure in para 1a does give a config option for simultaneous call termination at both the OBi100 and OBi110 on inbound POTS calls. Where 1b presents a config for call terminations at only the OBi100.
I had examined the Admin Guide, as suggested, and after spending time with it, it pointed to the change that resolved my outbound calling when ",Li" was placed after {2000xxxxx>(MLi):Li} Digimap string.
If the {2000xxxxx>(MLi):Li} string inhibited all outbound POTS line calls, how will adding {ph}to the string as {2000xxxxx>(MLi):Li},{ph} permit dual outbound Stage One calling, and OBITALK calls to terminate at the OBi110?
Would {2000xxxxx>(MLi)},{:Li},{ph} be a more appropriate Digimap string? The only way to know is to try it.
I find that books are a tremendous resource, however hands-on always wins.
Thanks.
azrobert:
The OBi100 default SP1 (ITSP A) digit map might be causing your routing problem. It won't allow you to send a 10 digit number to Line. The primary route digit map is used to validate the dialed number. It contains rule "<1>xxxxxxxxxx" which prefixes a 10 digit number with a "1". When you dial 10 digits, 11 digits will be sent to the OBi110. If OBi110 (Mli) doesn't contain an 11 digit rule then "{2000xxxxx>(Mli):li}" will not get a match and the call will fail. Just remove the "<1>" to fix the problem.
drgeoff,
I didn't know a vg can be used with obitalk. I tried it w/o a password and it worked.
Thanks
drgeoff:
Quote from: azrobert on April 29, 2020, 12:31:51 pm
I didn't know a vg can be used with obitalk.
That was the original use. The additional ability to use it as an outward only, no registration SP came with firmware v1.2 according to page 131 of the Admin Guide in the paragraph preceding the bullet points.
Navigation
[0] Message Index
[#] Next page
[*] Previous page