your ephone-dn have dual-line, so they will automatically have call waiting when a second call comes in. Probably you do not the second call because the 7902 have no display. Either configure the ephone-dn without dual-line, or with 'huntstop channel'.
Also, you can configure names, labels etc directly under the ephone-dn without using 'directory entry'.
Just to add a note Paolo's good info (also posted on End user Thread.)
Because this DN is set up as dual-line you need to add the following. Have a look;
The following example creates an ephone-dn with the number 1001 in dual-line mode. The no huntstop command allows calls to continue to hunt to other ephone-dns if this one is busy or does not answer. The huntstop channel command disables call hunting to the second channel of this ephone-dn if the first channel is busy or does not answer.
Actually I'm a bit puzzled by the fact that one needs 'huntstop channel' to forward on no answer. Logic would suggest that if a call is not answered on the first channel, no much more chances are that it will be on the second. But perhaps there are reasons not immediately understood for this.
As Rob mentioned, dual-line ephone-dn's support call waiting.
An incoming call will attempt to hit the first channel of the ephone-dn. If that channel is busy (because the user is on a call) then the call will immediately hunt to the second channel, at which point the user will see the second incoming call on their display (assuming the phone has one) and will hear call-waiting beeps.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...