SRST questions dial-plan CoR and conference 12.2 15 T2 1760
Currently running 12.2 15 T2
max-conf Is it supported on 1760 running Version 12.2(15)T2
The command is not available under global config mode call-manager-fallback although the below output states that we can have a max of 4 in SRST mode the soft key is not available on the phone.I did read some DOCS that said maximum of 8 conferences with 3 parties in each for a total of 24 is this for SRST version 3 only ?
I would like to set-up CoR class of restriction for some lobby phones whilst in SRST mode.
Is there a way to implement this scenario can it be done ? phones have faild over to SRST-->I would like to restrict directory numbers 4000 and 4001 so it(the phone) can only dial internal numbers 4XXX whilst in SRTS mode using CoR.
can the the CoR happen on the dial-peer voice 20001 pots below ?
The below output is from sh call-manager-fallback dial-peer command whilst in SRST mode.
Phone 7960 is in SRST mode with 2 extensions.
Currently I have only 1 dial-peer voice 1 pots dest patt 0 e1 ---->pstn
I'm also having issues coming to grips with translation rules where i'm wanting to create a dial-plan for our other offices wherby users dial the 5 digit ext and the call gets transformed to full number and out the pSTN ,when in SRST mode.Under call-manager-fallback I can only assign 1 translation with 10 rules as you can see i have many more.
Is there a easier way or simply way anyway to do this better.
limit-dn 7910 2
limit-dn 7940 2
limit-dn 7960 2
timeouts interdigit 5
access-code pri 0 direct-inward-dial
translate called 3 (Am i limited to 1 translation with 10 rules for translate ?This is how it appears to me any work around.)
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.