Incoming calls on pots line port not ringing through to the phone.
gary-gary:
Quote from: ianobi
Congrats on your detailed investigation and just reward!
Well it appears that congratulations may be a bit premature... it works sometimes and sometimes it doesn't. When it doesn't, it is back to the ring/dial-tone/ring again operation. :-(
Quote
Quote
GenerateCPCSignal: "For inbound and outbound calls" --> "For outbound calls only"
I don't think I would ever have thought of that. I don't remember it being an issue ever before in any country.
It seems that this change has had an unexpected side effect. One can no longer dial '#' to get to the pots line. Instead the OBi gives a message to the effect that this service had not been configured. :-(
Quote
Normally setting RingDelay to 0 means the OBi loses the ability to detect CallerID on incoming calls as this comes in after that first ring in North America. However, this PBX is so weird that maybe it sends it before the first ring - standard in UK and some other countries. This will be obvious by looking at Call History.
That was my understanding of RingDelay as well, but setting it to anything other than '0' results in no ring.
Yesterday my parents had a visit by a tech from the outside firm which manages the PBX (a Mitel 3300). I was on the phone with him and viewing/changing OBi settings remotely as we tried to debug this.
He was not able to answer my questions regarding the PBX's implementation of CPC or polarity reversal, but said he'd look into them.
One item he noted was that when I called the pots line, the phone attached to the OBi did a strange ring. Remember I'm calling from outside the PBX, so it generates a double-ring... but what he heard from the OBi's phone was more like a short ring and a half. Shouldn't this be RingProfile A, DefaultRing 1 as configured under the Line Port settings?
So this brings up another question... must the incoming ring pattern match one of these listed in the associated ring profile (A in this case)... for the phone to ring? And has setting ringdelay to '0' effectively disabled this? Is the OBi somehow interpreting the incoming call as ring-hangup-ring-hangup?
I've been trying to locate some audio samples of Bellcore-dr1 etc for comparison, but have been unsuccessful so far.
-gary
ianobi:
Quote
So this brings up another question... must the incoming ring pattern match one of these listed in the associated ring profile (A in this case)... for the phone to ring? And has setting ringdelay to '0' effectively disabled this? Is the OBi somehow interpreting the incoming call as ring-hangup-ring-hangup?
There's quite a lot to unpick here. The incoming ring pattern has no connection with the Ring Profile. The OBi just needs to detect some sort of ringing. The RingDelay setting has no effect on detecting the incoming ring.
I think that you are correct that that the OBI is seeing ring-hangup-ring-hangup. The odd ring at the phone is probably due to the OBi hanging up before the phone has completed ringing. I think the "double ring" from the Mitel is this pattern:
(.4+.2,.4+2) - ring for .4s, silence for .2s. ring for .4s, silence for 2s.
The standard North American ringing (Mitel internal extensions?) is
(2+4) - ring for 2s, silence for 4s.
I'm not sure what any of that proves, except that I believe that the problem is still a question of ring detection. A ring is being detected but the following silence is being detected as a hangup. It may be worth trying to increase RingTimeout, which should make the OBi think that the ringing is lasting longer. Also, at least for now, disable all PSTN Disconnect Detection "Detect" settings.
Quote
One can no longer dial '#' to get to the pots line.
This is very odd. Does the Phone Port OutboundCallRoute still have the following rule:
{(<#:>|911):li}
It would be helpful to have the actual spec for the Mitel 3300 analogue interface. I think we have a Mitel engineer somewhere on this forum. I will ask around.
Navigation
[0] Message Index
[*] Previous page