Meet-Me conference access code
UC500 Rss Feed
Popular Tags
Active forum topics
Voice News
- Pork n' beans
- Wine and Food in Seattle
- New Content on Tech Target - Unified Communications
- Mobile Broadband Growing, But Fixed Still Rules
- Berry Me or Be Cool and Bold
- Editorial Advisory Board Appointment - Business Trends Quarterly
- Disclosing the Double Standard
- Unmasking Caller ID With Asterisk
- Lots of Site Changes Coming
- The Future of How VoIP Will Be Purchased
- HUD 3 is Very Impressive
- Is High Definition Call Quality the True Promise of VoIP?
Cisco TAC Issues - CME - UE
- CUE 3.1 - Cannot change greeting using VoiceView Express , Fixed CSCsm00802
- CUE 3.1.1 Editor Express default menu Cancel Key, * , is incorrect , Fixed CSCsm71506
- Playback and Recording messages may fail through VoiceView , Fixed CSCsm35448
- CUE Name info for Voicemail notification , Open CSCsq21375
- The Notification call should come from VM not from AA. , Open CSCsd01014
You can do this with a
You can do this with a custom alias Feature Access Code. You can set this up as a speed dial, also. Make the FAC start with AA, as an example so no one can directly dial the MeetMe number.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/...
-Dapunisher
A+. Network+, MCP, CCNA, CCVP
Meet Me access code.
Users from outside the office will not have a "MeetMe" softkey on there phones so will not be able to setup the conference. They will only be able to join the conference after it has been setup.
On another note, does anyone know if there is a TCL script that enforces a pin number before entering a conference?
yup
yup. Nice comment.
Meet-Me Access code
To limit meet me access you need to set up Class of Restriction (COR)
a little bit more about COR is posted here
http://uc500.com/class-restriction
I'm wondering the same
I'm wondering the same thing.
meetme authentiation
This is a workaround, not an officially supported solution.
We use an inbuilt TCL script that is supplied in the IOS image called 'clid_authen_collect'. This script authenticates the call with the ANI (Calling number) and DNIS (Called number) of the incoming call, or if this fails, it then prompts the user to enter an account number and then a PIN number. Since the call is coming in on an FXO (or FXS) port, there is no associated ANI and DNIS, so the script immediately prompts the user for the account number and PIN. We do the authentication by a local 'username XXX password YYY' command in the router config. The user keys in the account code and PIN (can use the # as a string terminator to speed the process up and if the values entered match a local username and password, it then prompts for the user to enter the actual destination telephone number.
The router needs the following files on the flash memory to run the TCL script correctly:
enter_account.au
auth_fail_retry.au
enter_pin.au
enter_destination.au
The *.au files are the audio prompts that the IVR plays. These are standard SUN/next 64Kbps ulaw audio format. You can use an audio editor application such as Adobe Audition to create and save the prompts.
A caller will ring in on port 0/2/0 and be prompted to enter the account number and a PIN, and then an internal telephone number (could be an IP phone or the meet me conference number)
The audio files can be found at:
http://www.cisco.com/cgi-bin/tablebuild.pl/tclware
Look for, TCLware.2.0.1.zip