Polycom 3725-76302-001O Manual De Usuario

Descargar
Página de 425
 
Call Server Configuration
Polycom, Inc. 
250
Resolve to Lync conference 
ID
Resolves to a Lync conference that resides on a selected SIP peer.
When selected, the following fields are available:
Conference template 
When checked, you can select the conference template used to start the 
conference. If left unchecked, or if checked and unchanged, the Default 
conference template
 configured in Admin > Conference Manager > 
Conference Settings
 will be used. Keep in mind that the conference template 
must specify a Conference mode of AVC only, or the conference will not start. 
See the note on page 
.
Available SIP peers / Selected SIP peers selection area
This area lists the names of Available SIP peers and any Selected SIP peers
With the provided arrow buttons, you can move SIP peers between the Available 
and Selected areas. When this dial rule is executed, the system will query the 
selected SIP peers to find which one is hosting the Lync conference.
Note: For an external SIP Peer to be listed in the Available SIP peers area, it must 
be listed on the Network > External SIP Peers page and have the following 
configuration:
A Type of Microsoft 
The Enable combined RealPresence-Lync scheduled conferences 
check box selected in the Lync Integration tab
Note: We recommend ordering this rule so that it appears before any rule with the 
action Resolve to external SIP peer. If the Resolve to external SIP peer dial rule 
doesn’t successfully route a call, the call is aborted and no subsequent dial rules 
will be attempted. We also recommend that this rule not appear higher than its 
default order in the list of dial rules, because this can prevent valid aliases, VMRs, 
and VEQs from being dialed and can result in reduced system performance.
Resolve to service prefix 
Looks for a service prefix that matches the beginning of the dial string (not counting 
the URI scheme, if present). 
Note: For a SIP peer, the dial string must either include the protocol or consist of 
only the prefix and user name (no @domain). For instance, if the SIP peer’s prefix 
is 123, the dial string for a call to alice@polycom.com must be one of the following: 
sip:123alice@polycom.com 
123alice 
Resolve to external SIP peer 
Checks the domain of the dial string against all of the rule’s selected peers, looking 
for a peer proxy responsible for that domain. If the dial string matches the domain 
of one of the selected SIP peers, this rule will either successfully route the call, or 
the call will be aborted; no subsequent dial rules will be attempted.
After selecting this action for a rule, move the SIP peers to which the rule applies 
from the Available SIP peers box to the Selected SIP peers box. 
Note: This action employs the H.323<->SIP gateway function if applicable. 
Resolve to external 
gatekeeper 
If the dial string appears to be an H.323 alias, simultaneously sends LRQ 
messages to all of the rule’s selected gatekeepers. 
After selecting this action for a rule, move the gatekeepers to which the rule applies 
from the Available gatekeepers box to the Selected gatekeepers box. 
Note: This action employs the H.323<->SIP gateway function if applicable. 
For this action: 
The system attempts to resolve the address as follows: