how do you set-up call waiting on a UC520 with 7975G phones. The line type I have set to dual and the most phones are shared extentions between two phones. Right now when a second call comes in on a SIP DID it goes straight to the PMB. How to you set-up call waiting. Everythign I have read says it should be enabled by default , yet, for me,, not so much!
I think I know, it is the extention numbers and DID and username password assigned to a device. Currently it is set to huntstop channel and you are telling me to mak it no-huntstop channel. The issue is that I still don;t get the syntax.
I did: ephone-dn 14 and I get the reponce "bad IP or hostname"
For those of you who stuumble across this thred with very little Cisco experence wondering why call waiting does not work. well one possibility is when you activate a shared line in CCA it turns the call waiting off!
open a command prompt, go to your start bar and in the run filed type cmd and hit enter. It is also located under start>all programs>accessories
type: telnet 10.1.1.1 assuming you are connected to the UC520
if telnet does not work it may be disabled in Windows vista and Windows 7 as it was for me
login to the UC520 the default is cisco/cisco unless you changed it in CCA
type: show run
this will pull up a very long list. Look for ephone-dn entrys. These are the telephone number routing/peramters for your phones. Look for the ephone number example 10,11,14 ect that is assigned to the phones call waiting is not working on. You can identify by username and password or MAC address write down the ephone numbers you need.
get back the UC520# symbol by pressing more all the way through the show run command you did.
type: config t
type: ephone-dn 14
assuming 14 is the affected phone, or else enter your ephone number you wrote down.
step 7 type: no huntstop channel
close the comand prompt
pay it forward and answer one thred on this forum with an easy step-by-step direction for other "non-CCIE's" to be able to help them with some other issue.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.