05-26-2013 12:35 PM - edited 03-18-2019 01:11 AM
Hi,
With the old scheduler it was possible to choose ISDN for callin participants.
With SmartScheduler you can choose "Call-in Participants" and "Calling in on audio" but you can't choose ISDN so the prevered protocol is SIP.
We have callin participants to call in via ISDN.
By using Scheduler via TMS you can Choose "Extern" and "ISDN" for callin, with Smart Scheduler you can't do so.
With SmartScheduler the informationmail contains no ISDN Callin-number.
With TMS Scheduler the mail contains ISDN Callin-number.
But your users should use SmartScheduler cause it's more easy to use than the Scheduler within TMS Administration Side.
Any ideals?
kind regards
Martin
Solved! Go to Solution.
06-04-2013 10:59 AM
Hi Martin,
Smart Scheduler only schedules external SIP clients. It doesn't do ISDN dial-in or external dial-out.
Potentially you could reserve ports for externals to dial-in. If your ISDN gateway can connect to your MCU it would work.
ISDN user calls ISDN gateway, then enters conference address to call in to MCU.
greetings
thomas
06-04-2013 10:59 AM
Hi Martin,
Smart Scheduler only schedules external SIP clients. It doesn't do ISDN dial-in or external dial-out.
Potentially you could reserve ports for externals to dial-in. If your ISDN gateway can connect to your MCU it would work.
ISDN user calls ISDN gateway, then enters conference address to call in to MCU.
greetings
thomas
06-06-2013 03:26 AM
Hi Tom,
So we should use TMS Schedule instead of TMS Smart Scheduler.
Thanx for the Information
Kind regards
Martin Plank
06-10-2013 12:12 AM
Hi Martin
yes
or
1. get rid of the isdn dial ins :-)
2. or reserve fixed poorts for dial in
3. or use the TMS sheduler
greetings
thomas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide