12-12-2012 01:12 AM - edited 03-18-2019 12:17 AM
ON the EX90s, when I select the Cisco VCS as teh Infrastructure option, it prompts me for
Username
Password
Domain
and
External Manager.
What username and password is this trying to authenticate against? Where is this configured? IS this done in TMS? I tried creating configuration options in TMS similiar to those I'd create for Jabber, but the EX90 doesn't ever pull a config.
I can simply add the VCS-Expressway as the SIP proxy to the EX90 configuration and it will register and place and receive calls just fine, but I'm trying to get the device to actually authenticate.
I've looked at the Device provisoning guide and the authenticating devices guide, and this topic does not seem to be addressed. Does anyone have any pointers or suggestions they can share?
thanks, in advance,
rf
Solved! Go to Solution.
12-12-2012 01:36 AM
The account details under System > Provisioning > Users
We set the following settings at present, but this would be deployment specific depending on how you want to work things - not a recommendation of the best way to do things, as it probably isn't but it works for our small office:
Conference AutoAnswer Mode | Off |
Conference DefaultCall Protocol | Sip |
H323 Profile Authentication LoginName | |
H323 Profile Authentication Mode | On |
H323 Profile Authentication Password | |
H323 Profile CallSetup Mode | Gatekeeper |
H323 Profile Gatekeeper Address | |
H323 Profile H323Alias ID | {username}.ex90@ |
NetworkServices MultiWay Address | {username}.meetme@ |
NetworkServices NTP Address | |
Phonebook Server Type | VCS |
Phonebook Server URL | phonebook@ |
Provisioning ExternalManager Address | |
Provisioning ExternalManager Domain | |
Provisioning Mode | VCS |
Public SIP Server Address | |
SIP Profile DefaultTransport | Tls |
SIP Profile Outbound | Off |
SIP Server Address | |
Time Zone | GMT (Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London) |
12-12-2012 01:17 AM
This would be the username and password that the user has datafilled in TMS for their provisioning account - should be the same username as Jabber uses but passwords could be different if jabber is doing AD authentication.
You'd also need to add the EX90 provisioning template (xml file) to TMS and create provisioning settings.
12-12-2012 01:21 AM
Thanks Guy,
The EX90 TC5.1.1 provisoning template has been uploaded. Do you have some recomended provisoning settings?
Also, is it trying to use the username and password created in the user account section or the provisoning username and password?
thx,
rf
12-12-2012 01:36 AM
The account details under System > Provisioning > Users
We set the following settings at present, but this would be deployment specific depending on how you want to work things - not a recommendation of the best way to do things, as it probably isn't but it works for our small office:
Conference AutoAnswer Mode | Off |
Conference DefaultCall Protocol | Sip |
H323 Profile Authentication LoginName | |
H323 Profile Authentication Mode | On |
H323 Profile Authentication Password | |
H323 Profile CallSetup Mode | Gatekeeper |
H323 Profile Gatekeeper Address | |
H323 Profile H323Alias ID | {username}.ex90@ |
NetworkServices MultiWay Address | {username}.meetme@ |
NetworkServices NTP Address | |
Phonebook Server Type | VCS |
Phonebook Server URL | phonebook@ |
Provisioning ExternalManager Address | |
Provisioning ExternalManager Domain | |
Provisioning Mode | VCS |
Public SIP Server Address | |
SIP Profile DefaultTransport | Tls |
SIP Profile Outbound | Off |
SIP Server Address | |
Time Zone | GMT (Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London) |
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