Incoming calls on pots line port not ringing through to the phone.
gary-gary:
Quote from: ianobi
I think Shale is on the right lines here:
http://www.obitalk.com/forum/index.php?topic=2923.msg40763#msg40763
It could be as simple as removing R38 and R39, then installing the relay.
I'm leaving my OBi in one piece for now - it's doing a job :)
Almost...
Yes, R38 & R39 must be removed. Q206 is the driver, D203/204 is the snubber for back-emf when the relay opens, C99 is a power supply cap. I hope to pull mine open here shortly when things quiet down a bit and confirm these items.
I suspect D150 & 151 are not involved with the deletion or addition of the relay. They appear to be part of some protective components for the phone line.
-gary
ianobi:
We look forward to the resurrection of the original OBi110 with full power fail capabilities :)
gary-gary:
OK, I have my parents OBi110 unit here.
I tested it with my FiOS POTS line and it passes the incoming call properly from the line to the phone. It also reports the On-Hook voltage as -45V, vs the -21V I see from their PBX.
I looked at the Call Status, and it correctly shows:
Call 1 Terminal 1 Terminal 2
Terminal ID LINE1 PHONE1
State ringing ringing
It will be interesting to see if this holds true once it is connected to the PBX again.
I did not notice any difference in the ring patterns between line1 and SP1 - both produced the usual single long ring.
Was there some other parameter I was supposed to check while I have it here? This test was basically to make sure the OBi110 was not defective, and it doesn't appear to be.
I did see my parents OBi has software version 1.30 (build 2781M), while my unit has 1.30 (build 2774). I wonder what the difference is between the two builds. ***6 tells me there is no update available for mine.
Another oddity... the digit map for the line port is:
(<10>[2-9]xxxxxx|xxxxxxxS4|1xxxxxxxxxx|xx.)
ObiTalk displays a red ! next to this, and has a check under the OBiTALK settings. Logging directly into the unit, I see the same data, but the 'default' box is not checked. I've made no changes to this parameter.
-gary
ianobi:
Looks to me like your parents OBi110 is working correctly and the problem is still to get "Ring Detect" working when it's connected to the PBX.
Quote
I did not notice any difference in the ring patterns between line1 and SP1 - both produced the usual single long ring.
The phone connected to the OBi110 does not follow the ring pattern of the ringing coming in from the Line Port. Each service (sp1, sp2, line, OBiTALK) can be set to ring the phone with different ring patterns for incoming calls on each service. This is set by RingProfile and DefaultRing for each service.
Quote
I did see my parents OBi has software version 1.30 (build 2781M), while my unit has 1.30 (build 2774).
I have never seen build 2781M before, both my OBi110's are build 2774.
Quote
(<10>[2-9]xxxxxx|xxxxxxxS4|1xxxxxxxxxx|xx.)
This is weird! You are the third person recently to report this digitmap. This rule <10>[2-9]xxxxxx will sabotage any call starting 2 to 9 by prepending "10" after seven digits have been dialled and sending those nine digits to line. The default digitmap is:
Physical Interfaces > LINE Port > DigitMap:
(xxxxxxxS4|1xxxxxxxxxx|xx.)
Either new OBi110's are being sent out with that extra wrong rule, or something in the setting up is putting it there. Either way it's a mistake - Obihai please note!
When you are convinced this OBi110 will work correctly attached to the PBX, let us know how your parents will use it. Which calls go via GV? I presume any eleven digits starting with "1". What is the number range of the four digit internal numbers? Where do seven and ten digits numbers need to go? With precise info a good digit map that does all the routing automatically can be configured.
Shale:
Note Gary-gary said in his initial posts ", or can dial 9 to get an outside line followed by a 10-digit number."
I am thinking something with a <9,,> will be called for.
Navigation
[0] Message Index
[#] Next page
[*] Previous page