Using the Obi 110 as an FXO and FXS Port for FreePBX
Ad_Hominem:
Note: Obi has released an updated firmware that corrects the X_UseRefer bug. So, I've added a section encouraging users to update to the latest firmware and I've also added back the instruction to enable X_UseRefer.
loonsailor:
Thanks very much for providing this guide. I've followed it, but not with complete success. My obi110 (firmware 1.3.0 build 2721) works fine as an asterisk trunk but only works partially as an extension. I can call the extension, and it works fine, but I have limited dialing ability from the phone on the obi110 FXS port. From it, I can dial out using the 1xxxxxxxxxx dial plan, but that's all I can do. I can't call another asterisk extension (three digits on my system), or use *codes, or use different trunks that I've set up with an asterisk prefix. Furthermore, when I do dial an outgoing call using 1..., it doesn't show up in my freepbx call log.
I've tried the digitmap suggested here, and the default, but neither allows me to dial another extension. When I try, I get about a 5 second pause, one single ring, another long pause, then a voice message that the number I just dialed is invalid. I'm not sure whether that message comes from the obi, or asterisk, or the trunk.
Any ideas?
Thanks, in advance, for any help.
zapattack:
You have just described the exact same failure that my new 110 exhibits when dialing specific numbers
on the PSTN.
6043252011 is a 1000Hz test tone that answers and sends tone immediately in my local switch.
6043252091 is a 2-way test line that answers after about 1 second and sends a brief tone.
Neither line sends Ring Back Tone before connecting using #604325xxxx.
However, if I dial **86043252011 on the 110, I get a pause, 1 ring and then a PSTN time-out recording,
so the 110 has not successfuly connected.
But, if I dial **86043252091 I get a single Obi ring followed by connection to the test line.
Why is the 110 inserting a ring and why does it not connect immediately to either line?
Using updated software with no digit map modifications.
The only difference between the 2 numbers is speed of answer supervision.
****Answer. On the Line Port page there is a Detect Outbound Connect Method. If set to 'Assume connected after a short delay' it introduces the one ring. Detect Polarity Reversal, Detectect Speech, or None have no tone. Also note: on the ObiTalk Dashboard Expert configuration, the Assume option is missing.
greenhornet:
Any Ideas on why my caller ID would not be working on this setup? I can see caller ID on a phone connected to the phone port as well as on the obi call history portal. I know it's being passed and OBI is seeing it. I replaced a dead SPA3000 with the OBI and previously had caller ID working this way. FreePBX had no problems showing it. I have tried adjusting the ring delay. Not that it matters, since i can see the ID on an attached phone.
greenhornet:
No one has any caller ID suggestions? OBI support referred me to the forums on this problem. Their words, "Please post your question in our forum. Other members who has done this can help you in there."
Navigation
[0] Message Index
[#] Next page
[*] Previous page