Two Point Foreign Exchange (FX) Telephone Calling (OBI100/OBI110)
NYGuard:
Azrobert
The circuit works both ways as initially provisioned, and later with changes during the troubleshooting process. Sometimes the "book" may not be always correct. My experience with Telecommunication products has revealed capabilities that are not be captured by documentation.
Think of it in terms of an Easter Egg find. I have discovered, and exploited non-standard signaling combinations with TDM voice channel equipment in the past where developers did not know existed. Of course there is a risk of losing a hidden find during a future firmware update that removes it, because the item was not accounted for during regression tests. Firmware updates have been known to lose capabilities, but regression testing typically finds it.
The one thing that I didn't test was a OBiTALK end to end connectivity. Something to do by using Digimap argument string combinations to determine what will work.
Lastly, I was able to achieve a circuit function that I have been seeking for a long some time. Most post on the Forum were very close to the circuit function I was looking for. But most Q&A's were close, but not close enough.
If there was ever an RFI to the Forum requesting help for a same or similar FX configuration, I was not able to find it.
drgeoff's approach to my circuit configuration question was direct, and simple in terms of equipment configuration requirements. I was handed a 99% solution that helped tremendously to get to what I wanted to achieve; FX dial tone.
Thanks.
NYGuard:
Thread follow up. Please feel free to comment to observations.
Below are Digimap combinations, and test results made to the OBi110 ATA.
All calls were performed at the OBi100 phone port to PSTN# 1.800.555-1212 and OBiTALK# 200xxxxxx.
Modifications to the OBi110 OBiTALK Service Setting InboundCallRoute Digimap Configurations were made, with associated test call reference results as indicated, below:
{200xxxxxx>(MLi):Li},ph
Dial 1.800.555-1212, rings OBi110 Phone Port continually until answered, when OBi110 Line Port is not spare.
Dial 1.800.555-1212, rings OBi110 Phone Port continually until answered, if OBi110 Line Port is spare.
Dial ***9+9D OBiTALK number, call fails when OBi110 Line Port is not spare.
Dial ***9+9D OBiTALK number, call fails if OBi110 Line Port is spare.
{200xxxxxx>(MLi):Li},Li
Dial 1.800.555-1212, long pause, call completes OK.
Dial 1.800.555-1212, call fails if Line Port is spare.
Dial ***9+9D OBiTALK number, reach second dialtone. Re-enter 1.800.555-1212 on second dialtone to complete call OK.
Dial ***9+9D OBiTALK number, call fails if OBi110 Line Port is spare.
{200xxxxxx>(MLi):Li},Li,ph
Dial 1.800.555-1212 rings OBi110 Phone Port with two ring cycles, if call is not answered at the OBi110, call is passed automatically to the Line Port to complete OK.
Dial 1.800.555-1212 rings OBi110 Phone Port continually until answered, if OBi110 Line Port is spare.
Dial ***9+9D OBiTALK rings OBi110 Phone Port with one ring cycle, then second dialtone. Re-enter 1.800.555-1212 on second dialtone to complete call OK.
Dial ***9+9D OBiTALK rings OBi110 Phone Port continually until answered, if OBi110 Line Port is spare.
----------------------------------------------------------
{200xxxxxx>(MLi):Li},{ph}
Dial 1.800.555-1212, Long pause, continually rings OBi110 Phone Port when OBi110 Line Port is not spare.
Dial 1.800.555-1212, Long pause, continually rings OBi110 Phone Port if OBi110 Line Port is spare.
Dial ***9+9D OBiTALK number, call completes OK with OBi110 Line Port connected to a POTS line
Dial ***9+9D OBiTALK number, rings OBi110 Phone Port continually until answered, if OBi110 Line Port is spare.
{200xxxxxx>(MLi):Li},{Li}
Dial 1.800.555-1212, call completes OK
Dial 1.800.555-1212, call fails when OBi110 Line Port is spare.
Dial ***9+9D OBiTALK number, call fails if OBi110 Line Port is spare.
Dial ***9+9D OBiTALK number, long pause, reach second dialtone. Re-enter 1.800.555-1212 on second dialtone to complete call OK.
{200xxxxxx>(MLi):Li},{Li},{ph}
Dial 1.800.555-1212, call completes OK
Dial 1.800.555-1212, call fails when OBi110 Line Port is spare.
Dial ***9+9D OBiTALK number, long pause, reach second dialtone. Re-enter 1.800.555-1212 on second dialtone to complete call OK.
Dial ***9+9D OBiTALK number, call fails if OBi110 Line Port is spare.
Thanks again.
Side note: 1.800.555-1212 AT&T Toll Free Information Service: Recording states: AT&T Toll Free Information Service will be discontinued by AT&T on 01 June 2020.
drgeoff:
Your results do not correspond with what I recall either from some years of use of the OBi100 in Japan to the OBi110 in the UK or the OBi110 to OBi110 test setup that I did a few days ago. In both setups "Dialling through" never rang the phone on the 110 and calling the phone (**9, not ***9 as you have typed) never reached anywhere other than the phone whether the phone was answered or not. At this moment I'm not able to repeat that test but should be able to in the next day or two.
Your results make me think that the first rule in the InboundCallRoute is not working. Yet no matter how hard I look I see no difference in the format of what you post
{200xxxxxx>(MLi):Li},{ph}
and what works for me. That makes me query the 9 digit OBi number you are using. Are you sure that the 2000xxxxx is that of the OBi100 and not that of the OBi110? A further reason for my query is that both of my OBi110s have numbers that begin with 200 and my OBi100 has a 300xxxxxx number. To be absolutely clear, that number MUST be that of the calling, not called, OBi.
azrobert:
Try this for the obitalk InboundCallRoute:
{>(xx.):li},{ph}
NYGuard:
drgeoff
You are correct with a OBiTALK line number transposition. A cut and paste transcription error on my part.
Obitalk Service InboudCallRoute was: {200xxxxxx>(MLi):Li},ph
Changed to: {300xxxxxx>(MLi):Li},ph or {300xxxxxx>(MLi):Li},{ph}
The ph or {ph} designation change allows the POTS/OBiTALK to works both ways OK.
What is the significant between the two DigiMap options, ph and (ph}?
My apologies for dragging this out.
Thanks again, always.
NYG
Navigation
[0] Message Index
[#] Next page
[*] Previous page