Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
151
sipProxy=abc.acanopartners.com
trunkType=sip
priority=70
failureAction=continue
sipControlEncryption=auto
scope=callbridge
callBridge=0ce50c9e-c92b-43f8-9f79-69e638a9c098”
trunkType=sip
priority=70
failureAction=continue
sipControlEncryption=auto
scope=callbridge
callBridge=0ce50c9e-c92b-43f8-9f79-69e638a9c098”
These parameters are entered as one long strong concatenated with ampersands (&) as
shown below.
shown below.
If the API call is successful, 200OK status is seen.
7. To verify that the rule now applies, use a GET method on the “/outboundDialPlanRules/<
outbundDialPlanRule ID>” node where the node ID is ea3f5cd1-7b5b-4d80-af5f-
fffff2362d0f as before.
fffff2362d0f as before.
You also see the new rule in the Web Admin Interface. Note the “Call Bridge Scope” column
entry of “one” means that this rule only applies to a specific Call Bridge, not all Call Bridges.
entry of “one” means that this rule only applies to a specific Call Bridge, not all Call Bridges.
Appendix E API Examples