Note: In this document, a "system" refers to a complete Cisco Unified MeetingPlace site installation, which includes one active Application Server and one active Media Server. The system might also include one or more Web Servers.

About RSNA

RSNA

The Reservationless Single Number Access (RSNA) feature allows multiple Cisco Unified MeetingPlace systems to appear as one system to the user community. Any user who hosts (as a profiled user) or attends (as a profiled user or as a guest) a reservationless meeting can join the meeting by dialing the access phone number of the Cisco Unified MeetingPlace system that is local to that user, regardless of which system is hosting the meeting. Users are then redirected to the system that is hosting the meeting.

Dial Prefixes

Dial prefixes are applied to transfer addresses when call transfers are routed through Cisco IOS voice gateways. Cisco Unified MeetingPlace uses the first applicable method in Table: Options for Configuring Dial Prefixes to determine the dial prefix for each remote server.

Table: Options for Configuring Dial Prefixes

Method

How and When to Use This Method

1

Extended dial prefix

Use this option to control the type of codec used when performing call transfers between particular Cisco Unified MeetingPlace systems.

You configure the Routing Unit Number and Routing Codec fields with non-default values for each remote server. The system uses the configured values to create a four-digit dial prefix UUCC, where:

UU is the Routing Unit Number (with a leading 0 if necessary)

CC represents the codec

The codec digits are:

G.711U-01

G.711A-02

G.729-03

G.729a-04

G.729b-05

G.722-06

ILBC-07

Note: On the Cisco IOS voice gateway, make sure that you specify the same codec in the dial peer configuration.

Use this option when you want all Cisco Unified MeetingPlace systems to use the same dial prefix and the same codec for all call transfers.

You configure the Dial prefix field on the Remote Server Configuration Page so that the field is not blank. The system uses the configured Dial prefix for all remote servers. To enable the Dial prefix field, the Routing Codec field must be set to None.

Related Topics

RSNA Reserved Meeting Server

The RSNA Reserved Meeting Server feature allows a single Application Server to host reserved meetings within an RSNA-based network. Typically, all meeting reservations are on the one designated Reserved Meeting Server. When users attend meetings by accessing their local server, if their local server does not recognize the meeting ID, it transfers the user to the Reserved Meeting Server.

Note: You must synchronize the server times between the local Application Server and the Reserved Meeting Server.

The local server attempts to transfer calls to the Reserved Meeting Server if all of these conditions are true:

The Reserved Meeting Server feature has been configured on the local server:

The local server must be configured with a remote server record in which the Reserved Meeting Server check box is checked.

If you want any user profiles to identify the remote Reserved Meeting Server as the Schedule home server, create a duplicate remote server record in which you do the following:

Do NOT check the Reserved Meeting Server check box.

Enter a Home Server number in the range 0 to 999.

Make sure that all other fields are identical between the duplicate records for the Reserved Meeting Server.

The meeting ID that the user entered does not match the meeting ID of any meetings scheduled around that time on the local server.

The meeting ID that the user entered does not match any user profile, active or not.

The user confirms the meeting ID.

In addition, consider the following behavior of the RSNA Reserved Meeting Server feature:

This feature does not prevent meetings from being scheduled locally and will not warn or transfer a user who attempts to schedule a meeting locally.

If a meeting is scheduled on a server other than the Reserved Meeting Server, this feature will not facilitate attendance of that meeting.

A locally scheduled meeting always takes precedence over a remote one. This rule applies even if a local meeting recently ended and the user hears that meeting is over.

If the meeting does not exist on the remote system, the system prompts the user for a meeting ID after the transfer.

Meeting recordings are stored only on the Web Server that is associated with the Schedule home server for the meeting owner. To access meeting recordings, the users must know the URL of the Web Server that you assigned to the meeting owner.

The system cannot strongly authenticate users by password when they are transferred between servers. This causes the following restrictions for profiled users who are transferred into a meeting:

Repeat Step 3 through Step 5 to add a server entry for each remote RSNA system.

(Optional) Complete these steps to configure a Common dial prefix to apply to all call transfers.

Note: If you configure the Dial prefix, all RSNA systems must use the same dial prefix. For simplicity, we recommend that you instead configure each RSNA system to use the Default dial prefix. For details, see the Dial Prefixes.

You perform this task in the Cisco Unified Communications Manager Administration pages. Because the pages and menus vary by release, you should check the Cisco Unified Communications Manager Administration online help for step-by-step instructions that are specific to your release.

Procedure

Go to http://ccm-server/, where ccm-server is the fully-qualified domain name or IP address of the Cisco Unified Communications Manager server.

Before You Begin

You perform this task in the Cisco Unified Communications Manager Administration pages. Because the pages and menus vary by release, you should check the Cisco Unified Communications Manager Administration online help for step-by-step instructions that are specific to your release.

Restriction

By associating a SIP route pattern to a SIP trunk, you can no longer put the SIP trunk in a route group. If, for some reason, you need to put the SIP trunk in a route group, create duplicate SIP trunks. Specifically, for each SIP trunk that is associated with a SIP route pattern, create an identical SIP trunk that is not associated with a SIP route pattern.

Procedure

Go to http://ccm-server/, where ccm-server is the fully-qualified domain name or IP address of the Cisco Unified Communications Manager server.

Before You Begin

You perform this task in the Cisco IOS command-line interface (CLI) of the router. For more information about the Cisco IOS commands used in this procedure, see the Cisco IOS Commands Master List for your Cisco IOS software major release.

Procedure

On the Cisco IOS voice gateway for the remote Cisco Unified MeetingPlace system, enter privileged EXEC mode or any other security level set by a system administrator. Enter your password if prompted.

The number is one or more digits that identify the dial peer. Valid entries are from 1 to 2147483647.

(Optional) Provide a comment or description to help you remember what is attached to this interface.

Router(config-dialpeer)# description string

Route calls to the remote system:

Router(config-dialpeer)# destination-pattern digits

For Cisco Unified MeetingPlace Release 8.0, the destination pattern must match the dial prefix for the remote server. See the Dial Prefixes.

For the Extended RSNA Prefix feature, the dial-peer destination pattern must match the Extended Prefix string on the originating Cisco Unified MeetingPlace Application Server for the server being transferred to.

Configure the dial peer to use SIP.

Router(config-dialpeer)# session protocol sipv2

Configure any IP address.

Router(config-dialpeer)# session target ipv4:ip-address

The target IP address is ignored, but it is passed as part of the SIP REFER command. When the voice gateway receives a SIP REFER request with the string matching the RSNA dial peer, the voice gateway forwards the call to the target Cisco Unified MeetingPlace Application Server.

Figure: Direct Connection Between a PSTN Gateway and the Application Server using Extended Dial Prefixes

On the Application Servers in this example, configuring the Routing Codec field on the Application Server results in the extended prefix values shown in Table: Extended Prefix Values.

Table: Extended Prefix Values

Server

Extended Prefix

US1

0101

US2

0201

Note that the actual codec used when transferring calls depends on the dial-peer configuration on the gateway, not on the value of the Routing Codec field. Any codec (other than None) can be chosen for the Routing Codec field to generate the extended prefix. However, the codec you choose for a given server should be consistent across both of the Application Servers to generate the same extended prefix for that server.

Given these prefix values, the U.S. voice gateway would be configured with dial peers that match the extended prefixes: