Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
100
Dial plan rules are tried in the order of the Priority values. In the current Meeting Server version
only one match is possible for a call and even if there would be other matches in lower priority
rules they will not be reached; therefore the Priority setting is important.
only one match is possible for a call and even if there would be other matches in lower priority
rules they will not be reached; therefore the Priority setting is important.
CAUTION:
The default Encryption behavior mode is Auto. Ensure all "Lync" outbound dialing
rules are explicitly set to Encrypted mode to prevent the Call Bridge attempting to use
unencrypted TCP for these connections in the event of the TLS connection attempt failing.
unencrypted TCP for these connections in the event of the TLS connection attempt failing.
12.3.2 Incoming call page: call matching
The top table in the Incoming Call page is the Call Matching table. The rules defined in the Call
Matching table govern how the Meeting Server handles incoming SIP calls. Any call routed to
the Meeting Server on any domain can be tested for a match for IVRs, Cisco Meeting Appt users
or for preconfigured spaces on that server.
Matching table govern how the Meeting Server handles incoming SIP calls. Any call routed to
the Meeting Server on any domain can be tested for a match for IVRs, Cisco Meeting Appt users
or for preconfigured spaces on that server.
The example Call matching rule below seeks to match all calls coming in on the
meetingserver.example.com
domain to both Cisco Meeting App users and spaces.
For example, if the incoming call was to
name.space@meetingserver.example.com
and
there was a configured space called
name.space
the call would be routed to the space with
that name. If the incoming call was to
firstname.lastname@meetingserver.example.com
the
call would be routed to that user with that first and last name.
Alternatively, you can choose not to route calls to users or spaces on a per domain basis; that is,
you can use one incoming domain for spaces and another for users.
you can use one incoming domain for spaces and another for users.
After a rule is executed rules further down the list are ignored for the call.
If all Call Matching rules fail, the next table (Call Forwarding) is used as described in the next
section.
section.
Points to note:
n
Matching for space and/or users is only done on the part of the URI before the @.
n
You cannot configure more than one rule with same destination.
n
Do not leave the Domain field blank in a rule, otherwise the Call Bridge will refuse the call.
n
No rules in the Call matching table will result in all domains being matched.
n
The highest priority incoming call matching rule which will match for a space will determine
the domain shown in the client and in the invitation for that space.
the domain shown in the client and in the invitation for that space.
12 Dial plan configuration – integrating Lync