Getting 403 error when trying to call phone book Get List API on secondary Finesse server

[upchaurasia]

Hi,

We are getting 403 error code when trying to get phone book list from secondary finesse server.

What could be the reason? Generally 403 error returns by the configuration APIs.

Thanks & Regards,

Umesh

[dekwan]

Hi,

Is the same API working fine on the primary Finesse server? Or is it giving the same error.

A 403 usually means that the credentials are right, but that user doesn't have the permissions to use that API. The PhoneBook - Get List API can only be used by the administrator (https://developer.cisco.com/docs/finesse/#!phonebookget-list). Are you using administrator crednetials?

Thanx,

Denise

[upchaurasia]

Thanks for reply Denise. With primary server it's running fine and returning phone book and respective contact list.

• Phone books and contact lists created in primary finesse server should synchronized in secondary finesse server. If this is not happening it means there is issue in DB replication. Am I right? Because phone book & contacts not visible in secondary finesse server.
• Can you please confirm if primary finesse server is up then there is no issue if we are trying to get phone book & contact list from secondary finesse server?
• Generally 403 error comes, if we try to run configuration API(like creating ,modifying, deleting phone book and other items) with secondary finesse server but getting phone books and respective contacts are not configuration API.
• What error will come if phone book not available on secondary server?

I will check with site engineer and make sure that user configured is right. Any other reasons of 403 error??

Thanks & Regards,

Umesh

[dekwan]

Hi,

I just remembered that you cannot run the configuration apis against the secondary server. Per the documentation, you will get a 403 when you do: https://developer.cisco.com/docs/finesse/#!phonebook-api-errors/phonebook-api-errors

Thanx,

Denise

[upchaurasia]

But "Phone Book - Get List" doesn't come under configuration API. I think creating, modifying & deleting comes under configuration API.

Can you please confirm that "Phone Book - Get List"  API comes under configuration API list?

Thanks & Regards,

Umesh

[dekwan]

Hi,

PhoneBook - Get List is a configuration API (https://developer.cisco.com/docs/finesse/#!phonebookget-list/phonebookget-list). You can see this from the navigation tree in the documentation and it specifically states that "This API allows an administrator to get a list of all global and team phone books."

Thanx,

Denise

[dekwan]

If you are trying to get a User's list of phone books, you need to use this API: https://developer.cisco.com/docs/finesse/#!userget-list-of-phone-books

Thanx,

Denise

[upchaurasia]

Thanks for reply Denise. Is this categorization for phone book came after Finesse release 11.0? 

Regards,

Umesh 

[dekwan]

Hi,

No, I see these APIs in the Finesse 10.0 docs: https://developer.cisco.com/docs/finesse/#!previous-documentation-pdfs/finesse-developer-and-javascript-guide

Thanx,

Denise

[upchaurasia]

Hi Denise,

As per "User—Get List of Phone Books" description -

This API allows a user to get a list of phone books and the first list of associated contacts for that user, based on the defined range (1 to 6000). Contacts are retrieved from the global phone books first, followed by the team phone books, up to the maximum limit of 6000. Cisco Finesse Release 12.5(1) onward, this API is deprecated.

So, going forward which API we need to call to get Phone Book Contacts.

We can not call Phone Book API as those are configuration API and configuration API can not execute on secondary Finesse server.

I don't see any other API for phone book contacts to run using user credentials.

Thanks & Regards,

Umesh

[dekwan]

Hi,

You want to use the TeamResource-Get Phone Books API: https://developer.cisco.com/docs/finesse/#!teamresourceget-phone-books

Thanx,

Denise

[deepaksharmainnovaccer]

I was also getting the same error while using UCCX 12.0 sandbox. I was using Mozilla RESTer to make the call. I figured the issue was that I was unknowingly sending some extra data with my API request. I changed the Request Mode to Clean Request and it started working.