User guide

Appendix 2 – Troubleshooting
When Movi looks for phone book information the message flow is:
Movi Cisco VCS
INFO
To: sip:phonebook@<domain>
From: <Username>@<domain>
Content-Type: application/tandberg-
phonebook+xml
<xml><searchstring><character(s)>
</searchstring>
Unauthorised
To: phonebook@<domain>
From: <Username>@<domain>
www-authenticate: Digest nonce
INFO
To: sip:phonebook@<domain>
From: <Username>@<domain>
Authorization: Digest nonce
Content-Type: application/tandberg-
phonebook+xml
<xml><searchstring><character(s)>
</searchstring>
OK
To: sip:phonebook@<domain>
From: <Username>@<domain>
Content-Type: application/tandberg-
phonebook+xml
<xml><searchResponse>
<DisplayName>
As more characters are typed in Movi’s Type name, number or address field, further INFO
messages (with Authorization header) are sent with more searchstring characters specified. For each
INFO message an OK comes back with the first 10 phone book entries that match that searchstring.
Note: Note 401 Unauthorized or 407 Proxy authentication required may extend the trace.
 Failure to get any response to the initial subscribe: the wrong Internal VCS / External VCS
values may have been configured (or DNS is wrongly converting the name to IP address).
 401 Unauthorized for a second time to the initial subscribe: the Username / Password
credentials on Movi do not match those configured in the authentication page of Cisco VCS.
 No OK to Register: check that the SIP domain configured in Movi matches the SIP domain
configured on Cisco VCS
- check that Allow and Deny lists are not blocking this registration
- check the VCS Event Log (Status > Logs > Event Log)
Cisco VCS Deployment Guide: Cisco VCS Expressway Starter Pack (X5.1) Page 23 of 28