Table Of Contents
maxsessions (ccn trigger jtapi)
M
Last Updated: May 1, 2006
maxsessions (ccn trigger jtapi)
maxsessions (ccn application)
To specify the maximum number of subscribers who can access an application simultaneously, use the maxsessions command in Cisco Unity Express configuration application mode. To set the number to 0, use the no form of this command.
maxsessions number
no maxsessions
Syntax Description
Command Modes
Configuration application
Command History
Examples
The following example sets the maximum number of subscribers who can access the autoattendant application simultaneously to 12.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn application autoattendant
se-10-0-0-0(config-application)# maxsessions 12se-10-0-0-0(config-application)# end
se-10-0-0-0(config)# exitRelated Commands
Configures the CCN applications, such as voice mail and auto attendant.
Displays the CCN application details.
maxsessions (ccn trigger jtapi)
To specify the maximum number of subscribers who can access a JTAPI trigger simultaneously, use the maxsessions command in Cisco Unity Express configuration trigger mode. To set the number to 0, use the no form of this command.
maxsessions number
no maxsessions
Syntax Description
Command Modes
Configuration trigger
Command History
Examples
The following example sets the maximum number of subscribers who can access the JTAPI phonenumber trigger simultaneously to 12.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn trigger jtapi phonenumber 1234
se-10-0-0-0(config-trigger)# maxsessions 12se-10-0-0-0(config-trigger)# end
se-10-0-0-0(config)# exitRelated Commands
maxsessions (ccn trigger sip)
To specify the maximum number of subscribers who can access a SIP trigger simultaneously, use the maxsessions command in Cisco Unity Express configuration trigger mode. To set the number to 0, use the no form of this command.
maxsessions number
no maxsessions
Syntax Description
Command Modes
Configuration trigger
Command History
Examples
The following example sets the maximum number of subscribers who can access the SIP phonenumber trigger simultaneously to 12.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn trigger sip phonenumber 1234
se-10-0-0-0(config-trigger)# maxsessions 12se-10-0-0-0(config-trigger)# end
se-10-0-0-0(config)# exitRelated Commands
maxsessions (IMAP)
To specify the maximum number of simultaneous IMAP sessions, use the maxsessions command in IMAP configuration mode. To set the number to the default value 50, use the no or default form of this command.
maxsessions number
no maxsessions
default maxsessions
Syntax Description
Defaults
The default number of sessions is 50.
Command Modes
IMAP configuration
Command History
Usage Guidelines
This command is not available on the AIM.
An error message appears if a value for number is greater than 50.
If a subscriber attempts to use the IMAP feature and the IMAP server is at its maximum number of sessions, the subscriber will see an error message.
Note
The IMAP server must be restarted for this value to become active.
Examples
The following example sets the maximum number of simultaneous IMAP sessions to 12.
se-10-0-0-0# config t
se-10-0-0-0(config)# service imap
se-10-0-0-0(config-application)# maxsessions 12se-10-0-0-0(config-application)# end
se-10-0-0-0(config)# exitRelated Commands
maxsteps (ccn engine)
To specify the maximum number of steps that can be executed in an application, use the maxsteps command in Cisco Unity Express configuration engine mode. This command does not have a no form.
maxsteps number
Syntax Description
number
Maximum number of steps that can be executed in an application. The default value is 1000. Maximum number of steps is 10,000.
Defaults
1000 steps
Command Modes
Configuration engine
Command History
Examples
The following example sets the maximum number of steps in an application to 500.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn engine
se-10-0-0-0(config-engine)# maxsteps 500se-10-0-0-0(config-engine)# end
se-10-0-0-0(config)# exitRelated Commands
mwi refresh
To refresh the message-waiting indicator (MWI) lights on one or more telephones, use the mwi refresh command in Cisco Unity Express EXEC mode.
mwi refresh {all | telephonenumber tel-number}
Syntax Description
all
Refreshes all telephones configured on the system.
telephonenumber tel-number
Refreshes the specified telephone number or extension.
Command Modes
Cisco Unity Express EXEC
Command History
Usage Guidelines
Use this command to update the MWI lights when they are not in synchronization with the stored voice messages.
Refreshing an extension that does not require it does not affect that extension.
Examples
The following example refreshes the MWIs for all telephones:se-10-0-0-0> enablese-10-0-0-0# mwi refresh allThe following example refreshes the MWI for extension 2015:
se-10-0-0-0> enablese-10-0-0-0# mwi refresh telephonenumber 2015
Related Commands
Displays a list of all configured groups.
Displays a list of all configured subscribers.
Displays the properties of the configured voice-mail system.
mwi sip
To set the message waiting indicator (MWI) notification mechanism, use the mwi sip command in Cisco Unity Express SIP configuration mode. To use the outcall mechanism, use the no or default form of this command.
mwi sip {outcall | sub-notify | unsolicited}
no mwi sip
default mwi sip
Syntax Description
Defaults
The default mechanism is outcall.
Command Modes
Cisco Unity Express SIP configuration
Command History
Usage Guidelines
Only Cisco Unified CME can use the SIP outcall mechanism for generating MWI notifications. Outcall will not work between Cisco Unity Express and a Cisco Unified Communications Manager system.
Note
The outcall option is available for backward compatibility. It is recommended that you use either sub-notify or unsolicited for the MWi notification option.
To use the outcall option, Cisco Unified CME must configure each ephone-dn that is registered to receive MWI notifications as follows:
ephone-dn 30number 8000....mwi on..ephone-dn 31number 8001....mwi offBoth Cisco Unified CME and Cisco Unified Communications Manager in SRST mode can use the sub-notify and unsolicited mechanisms for generating MWI notifications. With these mechanisms, the MWI notifications will reflect the accurate status of messages in a subscriber's voice mailbox.
After an ephone-dn is configured with the sub-notify option, Cisco Unified CME sends a Subscribe message to Cisco Unity Express to register the phone for MWI notifications. When a new voice message arrives in the voice mailbox for the ephone-dn, Cisco Unity Express updates the MWI status. If Cisco Unity Express does not receive the Subscribe message for the ephone-dn, Cisco Unity Express will not update the MWI status when a new message arrives.
To use the sub-notify option, Cisco Unified CME must configure each ephone-dn that is registered to receive MWI notifications as follows:
For Cisco IOS Releases Prior to 12.3(11)T07
telephony-service..mwi sip-server 10.100.9.6 transport udp port 5060number 2010.ephone-dn 35mwi sipFor Cisco IOS Releases 12.3(11)T07 and Later
sip-ua..mwi-server ipv4:10.100.9.6 transport udp port 5060number 2010.ephone-dn 35mwi sipFor Cisco SRST Mode
sip-ua..mwi-server ipv4:10.100.9.6 transport udp port 5060number 2010.call-manager-fallback.mwi relayThe unsolicited option does not require Cisco Unified CME to send a subscription request for each ephone-dn to Cisco Unity Express for MWI notifications. Cisco Unity Express sends Notify messages to Cisco Unified CME whenever the voice mailbox for any ephone-dn receives a new message. In this way, the MWI status reflects the current voice mailbox message status.
To use the unsolicited option, Cisco Unified CME must configure each ephone-dn that is registered to receive MWI notifications as follows:
For Cisco IOS Releases Prior to 12.3(11)T07
telephony-service..mwi sip-server 10.100.9.6 transport udp port 5060 unsolicitednumber 2010.ephone-dn 35mwi sipFor Cisco IOS Release 12.3(11)T07 and Later
sip-ua..mwi-server ipv4:10.100.9.6 transport udp port 5060 unsolicitednumber 2010.ephone-dn 35mwi sipFor Cisco SRST Modesip-ua..mwi-server ipv4:10.100.9.6 transport udp port 5060 unsolicitednumber 2010.call-manager-fallback.mwi relayThe SIP server IP address used in these commands must be the IP address of Cisco Unity Express. In the examples shown above, this is 10.100.9.6.
Examples
The following example configures the MWI notification mechanism as SIP Notify:
se-10-0-0-0# config tse-10-0-0-0(config)# ccn subsystem sipse-10-0-0-0(config-sip)# mwi sip sub-notifyse-10-0-0-0(config-sip)# endse-10-0-0-0(config)# endse-10-0-0-0#Related Commands
