MD110 shows calling even after call is answered

[vom1218]

When calling some numbers the phone displays "Calling..." even after the call has been answered. An example is the AT&T Teleconference number 866-621-2140.

Unfortunately, the keypad is disabled while in that state so you can't enter the code to join a conference.

Is there a fix or workaround for this problem?

 

[LifeSentence]

You need to make sure that all trunk routes used in the connection of this call have the appropriate settings for the answer signal that may or may not be sent to or expected by the originating trunk route. These parameters are normally set in the SIG parameter of the ROCAI command and there are also parameters in the RODAI command. If this is a call to the PSTN then the telephone exchange must send an answer signal if the PABX Trunk Route is programmed to expect an answer signal.

Good luck
Regards

But, it worked in the lab!!

 

[mdman]

There are free-of-charge numbers that do not send a connect message (no connect = no charge) instead of sending an AOC message that states that it is free-of-charge. Since no CONNECT is received you cannot enter DTMF digits.
In this case you can set ADC D18 in RODDI to fake an internal b-answer. This should only be used for calls to such numbers, do not switch this on for all calls. The reason for this is that the call states do not reflect the real situation anymore,f.e. a call to a normal number will generate an internal CONNECT, then a CONNECT from the network is received, the md110 will send a STATUS message because that normally shouldn't happen. In the worse case your calls will be dropped.

You can use LCR to filter these numbers and route them via this destination.