Using the Obi 110 as an FXO and FXS Port for FreePBX
philc:
Quote from: greenhornet on March 05, 2013, 12:26:43 pm
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.
I'm assuming you followed the directions for setting this up using the OP's method? I can say that using his setup I have personally successfully got my Cisco SPA525G phone up and running with full caller ID (name & number).
Have you looked at the FreePBX logs? I can see Caller ID information for incoming calls clearly laid out in the logs. You may need to increase the FreePBX verbosity if you don't see enough info.
The challenge with these setups is the number of moving parts; specifically the OBI device, FreePBX, and the phone. Determining where the failure is occurring is very helpful. You have at least somewhat ruled out the OBI device. Next stop is getting your arms around FreePBX operation.
Good luck,
Phil
philc:
As I mentioned in my previous post, I have had great success setting up a Cisco SPA525G phone with an OBI 110 and FreePBX. I considered the various methods suggested by Michigan Telephone as well, but in the end decided to go with Ad Hominem's approach. Although I liked the cleanliness of using the Custom Trunk in MT's prescription, my desire to preserve caller ID name information I am receiving from my POTS line was a key requirement.
Once you get the hang of configuring FreePBX the ease and control of using prefixed "codes" (Step 6) really shines. I even went one step further and added a dial rule ("222" in my case) to allow for tapping into an active POTS line on the OBI device FXO. This was accomplished by adding another prefix ("87" in my case) to the 222 causing 87222 to be issued to the OBI device. I then added "{>(<87222:>):li}" to the X_InboundCallRoute in the SP2 service parameter. The FreePBX logs were very useful in showing how the numbers get added and stripped along the way. This is with the added dimension of running FreePBX in VirtualBox on Windows 7 (I used that to great effect when "moving" FreePBX to a different machine. I didn't even need to change the FreePBX network configuration since the MAC address came along with Virtual Box...same IP address, etc.).
Fwiw, I went one step further and hooked up 2 OBI 110's in this fashion which was simply a repeat of the basic configuration. As a result, I have 2 POTS lines and 2 GV lines all accessible on my 5 line phone (yes, 1 line is empty). Pretty sweet I would say.
So all in all a big thank you to Ad Hominem, Michigan Telephone, and others for allowing me to get this to work! The collective insight provided really made this possible.
I do have one remaining issue that I have not been able to overcome yet. I cannot get Call Waiting (much less CW ID) to function. Specifically, I can hear the beep when someone is calling while I'm on the line (no surprise since that is Switch generated), but I can't seem to identify a method to send a hook flash signal through FreePBX to OBI. There doesn't even appear to be a button the Cisco phone for this purpose. Any ideas on how I might solve this would be appreciated.
Thanks,
Phil
zapattack:
SPA525 will probably present a Soft Key to transfer to second call.
Check the screen.
Mattak:
Thank you so much for this guide! It is exactly what I wanted to use the Obi 110 for!
I'm having a few other issues though. I wonder if you guys can help?
1: It seems like there is a small issue with the Obi hanging up a call through PSTN.
If I make a call into the Obi from my mobile it rings and I can answer through where ever I have routed the call through asterisk. If I then hang up the call locally the call goes silent on the mobile but it still shows as connected. If I then try to dial out locally I just get connected to the same call and I hear asterisk trying to dial numbers in my mobile.
The strange thing is that on the Obi110 web page, after hanging up locally, the line port status shows as "On Hook" and call status shows 0 active calls.
It seems like the Obi110 or asterisk is failing to tell the PSTN that the call has ended and I would be relying on the incoming caller to hangup to end the call.
Any ideas?
2: I am unsure which settings to fiddle with to change the timings. Currently it takes 3 rings on my mobile before anything shows up in asterisk and a local phone starts ringing. It also seems to take a long time (around 9 seconds) to actually dial out from an analogue phone connected to the Obi110 to asterisk then back out the Obi110 to the PSTN.
3: I am in London in the UK and was wondering if anyone knows if there is a page that shows all the local tone settings and other defaults that are specific for the UK.
Thanks in advance! Keep up the great work!
Mattak
jaabello1:
Hi,
I have set up the OBI110 according to this explanation and it worked, but I want to know if i can use the OBI110 POTS to forward a call from an asterisk extension to an external number.
I mean, I route the inbound call from the PSTN line to asterisk, there, an IVR answers the phone, and if the extension doesn't answer, I want to forward the call to an external number, but using the OBI110 as the trunk.
Is it possible?
I'm getting this error "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 34"
thanks
Navigation
[0] Message Index
[#] Next page
[*] Previous page