|ASTERISK-08091: CallerID Callwaiting appears to be broken
|Larry Shields (larrys)
|Sometime shortly after Asterisk 1.2 was relased I noticed callwaiting callerID on my ATT line was not being displayed. I only hear the beep,beep that a call is waiting with no CID. If I am on the same ATT trunk and a call arrives from an IAX trunk I do get callwaiting callerID.
I have upgraded to the latest relased version of Zaptel 1.2.10.
I am running Asterisk 1.2.13
I have a TDM400 with 3 FXS and 1 FXO port.
I am running CentOS version 3 with the latest updates.
Caller ID on the initial inbound call works fine.
The Zapata.conf has the following parameter set for the FXO port:
rxgain=11 ; prev 12
txgain=-4.0 ; prev -3.5
channel => 4
****** ADDITIONAL INFORMATION ******
I have verified with a Sony and Uniden phone plugged directly into the trunk that CID and Callwaiting CID is enabled and functional from the CO.
I experimented by running a Asterisk server (A) with FXS port to another Asterisk server (B) with FXO. I then send a call through from A to B. The call rang in with CallerID on the initial call. When I sent a second call in from A to B, the phone beep to indicate a call was waiting but no callid was shown. On the console of Asterisk server (A) a message was displayed that the "CPE does not support CallerID Callwaiting".
|By: Joshua C. Colp (jcolp) 2006-11-21 12:07:54.000-0600
I wasn't aware that this was supported, did it work in an older version? I know on analog call waiting is a tone sent from the telco, and Asterisk has no idea... it just forwards the audio on. I know it works on coming from an IAX trunk because it's an actual separate call coming in.
By: Larry Shields (larrys) 2006-11-21 14:00:29.000-0600
Yes. I have been using Asterisk in my home office for three years now and it always worked perfectly. Some time shortly after I upgraded to 1.2 my wife brought to my attention that the CID was not being displayed when a call was waiting. We get the beeps but no CID. Although I am currently using a TDM400 I previously had a X100P FXO connected to the CO. As you can see from the links below CallWaiting/CallerID is specifically supported on both cards. This would have nothing to do with any additional VoIP trunks that may be terminating on the system. Because Asterisk is correctly facilitating CallWaiting/CallerID between FXO and VoIP trunks it makes me suspect the problem is with the Zaptel code not correctly passing the CallID during the Callwaiting event.
By: Joshua C. Colp (jcolp) 2006-11-21 14:04:52.000-0600
Since this is an issue with Digium hardware please take it up with Digium support at firstname.lastname@example.org or via the phone number. If it turns out to be a zaptel issue they'll bring it up with development.