Cisco TMS view issues

[Lonemaker]

Hi there,

I have set up a fresh TMS installation TMS 14.3 TMSPE 1.1 and after a reload I got a Portal error:

Also I am unable to view device details under the Navigator page... status remains in Loading...

Have anyone seen this before? Where to look for the issue? Thanks for help!

Update:

In addition I have also found an issue with the SmartScheduler, giving back:

"There was a problem connecting to the scheduler backend : Unspecified Error"

regards, 

[Magnus Ohm]

Again this might be an IIS error where the public folder does not allow anonymous access.

Please look here in this thread.

https://supportforums.cisco.com/message/3553358#3553358

It´s for phonebook but the phonebook API is also in the public folder together with the feedback (CDR). It could be many reasons for calls not getting recorded but again, this is the most common issue.

https://supportforums.cisco.com/message/4048746#4048746

Let us know if this helped you

/Magnus

[daleritc]

Agree and good points Magnus And again, and if IIS is the case, then not a product problem.

[Lonemaker]

Looks like the public folder has the correct access rights?

[Magnus Ohm]

Indeed it looks correct.

Can you tell me what kind of endpoints where involved in the conference? If you do an xstatus on the systems (depending on the systems involved of course) look for the "feedback address" field number 3. Can you see if there is an address there pointing to the TMS server?

like this:

xstat //httpfeedback 3

*s HttpFeedback 3 URL: "http:///tms/public/feedback/code.aspx"

*s HttpFeedback 3 Expression: "/History/CallLogs/Call"

*s HttpFeedback 3 Expression: "/Status/Call[Status='Connected']"

*s HttpFeedback 3 Expression: "/Status/H323/Gatekeeper"

*s HttpFeedback 3 Expression: "/Status/SIP/Registration"

*s HttpFeedback 3 Expression: "/Status/Network/Ethernet/Speed"

*s HttpFeedback 3 Expression: "/Event/CallSuccessful"

*s HttpFeedback 3 Expression: "/Event/Message/Prompt/Response"

Just to make sure the endpoint knows where to send the CDR. If it does not arrive at TMS, TMS cannot collect it and store it either.

/Magnus

[Lonemaker]

Endpoints are ex60 and sx20

Both have the following entrys set:

*s HttpFeedback 3 URL: "https://XXXXXXX/tms/public/feedback/code.aspx"

*s HttpFeedback 3 Expression: "/History/CallLogs/Call"

*s HttpFeedback 3 Expression: "/Status/Call[Status='Connected']"

*s HttpFeedback 3 Expression: "/Status/H323/Gatekeeper"

*s HttpFeedback 3 Expression: "/Status/SIP/Registration"

*s HttpFeedback 3 Expression: "/Status/Network/Ethernet/Speed"

*s HttpFeedback 3 Expression: "/Event/CallSuccessful"

*s HttpFeedback 3 Expression: "/Event/Message/Prompt/Response"

[daleritc]

Is the "xxxxxxx" an IP Address or DNS...meaning if DNS, can the EP resolve on it?

I also note your using HTTPS vs. HTTP, is everything wrt HTTPS correct?

[Lonemaker]

Sorry, yes this is an resolvable DNS entry by the endpoint. I hope that https is correct, but the phonebook is also using the https link https://xxxxxx/tms/public/external/phonebook/phonebookservice.asmx  and this works.

[Magnus Ohm]

I would start a wireshark trace on the TMS server before making a call between the endpoints. Make a quick call and hang up. The CDR generates a few seconds after you hung up. See if there is actually any incoming packets coming from the endpoints.

It might be easier working with a TAC engineer in a case then on this forum to resolve the issue as then you can have a remote session and they will probably find the issue right away.

/Magnus

[Lonemaker]

I thank you all for your help, i will contact TAC for the statistic issues.

But a last question, is it actually possible to change the smart schedular language?

[daleritc]

But a last question, is it actually possible to change the smart schedular language?

No but language support for SS is coming in the next release. Calendar Q114.

Sent from Cisco Technical Support iPad App

[Lonemaker]

Finally, I can say that all problems only on the basis of the incorrect language setting in SQL Server are created.

CCNP R&S