Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Conferencing Center 3.0 PRI bridge to S8500B

Status
Not open for further replies.

Ciszek

Vendor
Jan 25, 2005
7
US
Doin'my first one. Read tip 21(conference server solution but not the real Conferencing Center app) and CC I&A manual.

Tip 21 uses UDP/AAR to get the call across the link from S8500 to IPO and relies on VMPro to do pre-administered Check PIN events to get to the bridge. How should routing through S8500 to IPO VM Pro be set up if using Conferencing Center?

Looks to me like the web scheduler can generate random PIN numbers so how does the call get to the right bridge?

Not gettin it and feelin like a deer in the headlights...
 
- Route a number from the S8500 to the IPO.
- Create a shortcode with this number which goes to a module on the VM Pro
- In the module on the VM Pro add the conference center actions and customize the different results.

It's the VM Pro which will check the conference PINs and route the call into the correct bridge.
 
Thanks VOiDDude,
You recommend just sending the 4 digit DNIS to IPO and have those 4 digits as the short code?

When the conference host schedules a conf, it looks to me like a conf code is generated and then a PIN per user. If I've got that right, I assume the conf code is the same for everyone but the PIN is different for each participant. Does the module only check against the conf code?
 
Yes, the shortcode is all you need to route the call to the VM Pro.

You're right about the conf code, it's the same for everyone. Only the user PIN is different. As far as I know the module only checks against the conf code.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top