×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Howto provide additional phonebooks to Movi users

Unanswered Question
Mar 14th, 2012
User Badges:

Hi there,


I want to provide additional phonebooks to Movi users, how can this be done?

(Finally managed to provide Movi users phonebook to Movi users, this is not the problem)


Thanks

Juergen

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Martin Koch Wed, 03/14/2012 - 05:04
User Badges:
  • Red, 2250 points or more

Ok, then you know how you have set up the "provisioning" phonebook with the "Access Control".

You do the same with other phonebooks and select the movi groups which shall have access to it.


Remember this will be all a flat searchable structure, so sometimes some renaming of the entries can be very benificial for your users to find something.



Juergen Hornung Wed, 03/14/2012 - 05:24
User Badges:

Hi Martin,


as always a very warm thankyou for your explanations


Your explanied way is the same as I did before, but I have no success, even I logged out and in again.

Could that be a problem with update to VCS 7.1?

I realized that Movi users wont be marked as "acive" under Systems -> Systems -> Directory -> [Movi user]


Regards

Juergen

Martin Koch Wed, 03/14/2012 - 09:40
User Badges:
  • Red, 2250 points or more

Hi Juergen,


I have TMS13.1.2 with X7.1 running and it works fine.

I never really trusted the "active" system and license usage count anyhow, so this can

be a symptom, but it does not necessary have to be like that.


It can have multiple causes:

* sip domain settings

* zone authentication settings

* wrong phonebook settings in the prov.dir. (check that this points to the right domain).

* wrong access settings in the phonebook (really double check that the movi groups are selected)

* wrong phonebook entries (just set up a manual test source, connect that to a test phonebook and

and grant access to all provisioning folders and add test@test.com as a sip and h323 entry)

* provisioning key and sip routes present on VCSs where it should not be active

* replication issues (tms agent diagnostics ok?)

* firewall issues

* ...



Does it work for some clients, do you see any pattern? Do you have multiple VCS, ...?

Does at least the provisioning phonebook show up or none at all



Especially if you are thankful, please rate the postings by using the Stars below! ;-)

Actions

This Discussion