Filter
Top Products
Call Server Configuration
Polycom, Inc. 248
Resolve to Lync conference
ID
Queries an integrated Lync SIP peer for a Lync AVMCU-based conference with a
matching conference ID. This dial rule action enables Polycom RealConnect
TM
functionality. See Scheduled Conferences with Polycom RealConnect™.
When selected, the following fields are available:
• Conference template
When checked, you can select the conference template used to start the
conference. If you leave this option 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
Considerations and Requirements for Lync 2013 Integration.
• MCU pool order
Select the MCU pool order to use for MCUs that provide Lync AVMCU cascade
functionality. If you leave this option unchecked, the dial rule will use the default
pool order configured in the Default MCU pool order field on the Admin >
Conference Manager > Conference Settings 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 the 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 RealConnect
TM
conferences check box selected in the Lync
Integration tab
Note: Polycom recommends 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. Polycom also recommends 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
For this action: The system attempts to resolve the address as follows: