1. Brekeke Product Name and Version: SIP Server Version 2
2. Java version: Java 6 standard edition
3. OS type and the version:
4. UA (phone), gateway or other hardware/software involved: Rauland R5 integration to Cisco Call Manager.
5. Your problem: Some calls failing, patient gets a message user not available. For this application, the patient places a call from the bedside, and the call rings 7 handsets simultaneously. Whoever answers the call first talks to the patient. Facility reports the patient gets a message, just sometimes that the user is not available.
I see in the logs that error 404 pops up with a call failure note. One question I have, will the 404 pop up if the actual handset is turned off?
I know that the port, #, deploy pattern, dial string, and IP to call manager is correct because most calls go through. Just sometimes the patient is getting the user not available message through the bedside.
Thanks, -Tom
2. Java version: Java 6 standard edition
3. OS type and the version:
4. UA (phone), gateway or other hardware/software involved: Rauland R5 integration to Cisco Call Manager.
5. Your problem: Some calls failing, patient gets a message user not available. For this application, the patient places a call from the bedside, and the call rings 7 handsets simultaneously. Whoever answers the call first talks to the patient. Facility reports the patient gets a message, just sometimes that the user is not available.
I see in the logs that error 404 pops up with a call failure note. One question I have, will the 404 pop up if the actual handset is turned off?
I know that the port, #, deploy pattern, dial string, and IP to call manager is correct because most calls go through. Just sometimes the patient is getting the user not available message through the bedside.
Thanks, -Tom