Vpn callmanager exited with error 256

vpn callmanager exited with error 256

pptp call manager exited with error 256. I'm trying to set up my own VPN connection on Leap opensuse 42.2 using: [email protected]:~> following command pptpsetup. superuser.com › questions › pptp-vpn-works-from-windows-not-linux. This guide was created to help you when exiting vpn Call Manager with error code 256. Stop wasting time with computer errors.

Vpn callmanager exited with error 256 - sorry, that

Tips For Fixing PPTP Call Handler Exit With Error 256

If pptp Call Manager fails with error 256, today’s user guide has been written to help you.

pptp call manager exited with error 256

I’m trying to set up my own VPN connection on Leap opensuse 42.2 using:

I’m about to get an error message. Even if I mean mine, by disabling the firewall, I immediately get the corresponding error message. I was wondering if anyone knows how to fix the error.

Firm.off-topic

.Your answer is not currently accepted.

pptp call manager exited with error 256

Want to improve this update? question to make it aRelevant for and unix Linux Stack Exchange.

[Previous linked to list] [Next in list] [Previous in chain] [Next in chain]List: Ubuntu UsersSubject: Re: [SOLVED] PPTP VPN ErrorAuthor: De Paolo Michele

System Error Messages for Cisco Unified Communications Manager 11.5(1)

Note

Optional parameter is indicated with the notation {Optional}. Application or Component may decide not to use that parameter in the alarm message.

Order of the parameters in an alarm message can change and it is decided by the Application or Component.

If the error message contains UNKNOWN_PARAMNAME, the parameter immediately following the UNKNOWN_PARAMNAME has not yet been updated in the alarm catalog. If this occurs, the error message is given a severity-level of 3, irrespective of the default severity-level for that error message.


Error Message

%: %[Priority=String][AppID=String][ClusterID=String][NodeID=String]: Service is running and working properly.

Explanation   CMI service is running and working properly

Recommended Action   Informational purpose only; no action is required

Error Message

%: %[StopBit=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration.

Explanation   An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value

Error Message

%: %[Parity=String][AppID=String][ClusterID=String][NodeID=String]: The CMI service parameter, Parity, has an invalid configuration.

Explanation   An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value

Error Message

%: %[InvalidDN=String][AppID=String][ClusterID=String][NodeID=String]: SMDI message contains invalid DN.

Explanation   Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false

Error Message

%: %[SMDICmd=String][AppID=String][ClusterID=String][NodeID=String]: CMI receives an invalid incoming SMDI message.

Explanation   There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message doesn't have one of the acceptable formats as described.

Recommended Action   Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format

Error Message

%: %[OpeningError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to open the serial port, the operating system returns an error.

Explanation   For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.

Recommended Action   Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.

Error Message

%: %[GetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to get the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't get the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[SetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to set the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't set the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to write SMDI messages to the serial port.

Explanation   CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to read SMDI messages from the serial port.

Explanation   CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: The handle for the opened serial port is invalid.

Explanation   CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[VoiceMailDN=String][AppID=String][ClusterID=String][NodeID=String]: The Voice Mail DN for CMI is invalid.

Explanation   CMI can't register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (0-9). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: An error occurred when CMI tried to stop the CMI service.

Explanation   As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.

Recommended Action   Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).

Error Message

%: %[MemAllocFailure=String][AppID=String][ClusterID=String][NodeID=String]: CMI tried to allocate memory and failed.

Explanation   Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.

Recommended Action   Use the Real-Time Monitoring Tool to check performance counters related to system memory to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

Error Message

%: %[DBLException=String][AppID=String][ClusterID=String][NodeID=String]: Unable to connect to the DB.

Explanation   When CMI service is started, it tries to read CMI Service Parameters from DB. During this, if CMI cannot connect to the database, it triggers this alarm.

Recommended Action   Check Database connection, then restart CMI.

Error Message

%: %[CMIException=String][AppID=String][ClusterID=String][NodeID=String]: Error while reading the database.

Explanation   This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.

Recommended Action   Refer to the associated alarm for further information.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown error while connecting to DB.

Explanation   When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.

Recommended Action   Report to Customer Service representative.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Service is now running.

Explanation   CMI service has been started and running

Recommended Action   Informational purpose only; no action is required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Service is now stopping..

Explanation   CMI Service has been stopped.

Recommended Action   Informational purpose only; no action is required.

Error Message

%: %[DebugMsg=String][AppID=String][ClusterID=String][NodeID=String]: This alarm is generated only for the purpose of debugging.

Explanation   CMI has several debug messages which simulate the real-time situations

Recommended Action   Report to Customer Service representative

Error Message

%: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI can't establish connection with the Cisco Unified Communications Manager.

Explanation   CMI can't establish connection with the Unified Communications Manager

Recommended Action   Check the address/status of the CallManager and the network

Error Message

%: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI loses the connection with Unified Communications Manager.

Explanation   CMI loses the connection with the Cisco Unified Communications Manager

Recommended Action   Check the status of the Unified Communications Manager and the Network

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: Windows Socket startup failed.

Explanation   WinSock could not be started

Recommended Action   Report to Customer Service representative.

Error Message

%: %[ParaNameInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI service configuration parameter is not found in Database.

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Report to Customer Service representative to get the database upgrade

Error Message

%: %[COMException=String][AppID=String][ClusterID=String][NodeID=String]: CMI catches an COM exception..

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Check system setting and resource, then restart system.

Error Message

%: %[LastPDUNumber=Long][AppID=String][ClusterID=String][NodeID=String]: Application has dropped the connection to CTIManager.

Explanation   TCP or TLS connection between CTIManager and Application is disconnected

Recommended Action   Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert)

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Maximum number of application connections is reached; application connection rejected.

Explanation   Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed

Recommended Action   Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in www.cisco.com based on the version you are using for maximum number of applications and devices supported by CTI

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][PDUNumber=Long][AppID=String][ClusterID=String][NodeID=String]: An invalid QBE PDU is received.

Explanation   QBE PDU from application is invalid

Recommended Action   This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins)

Error Message

%: %[CTIconnectionId=Long][LoginUserId=String][Reason=Enum][IPaddress=String][IPv6address=String][AppID=String][ClusterID=String][NodeID=String]: CTI application failed to open provider; application startup failed.

Explanation   The application is unable to open provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Review the reason code and the recommended action within the reason code

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
0x8CCC0075 (2362179701)Login request to authenticate user has timed out. Possible causes include LDAP server misconfiguration such as LDAP server referrals misconfiguration or Unified CM node experiencing high CPU usage. Recommended action is to verify the CPU utilization is in the safe range for Unified CM (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCC0060 (2362179680)Directory login failed. Verify that credentials are not misconfigured, check the userID and password configured in the application matches with what is configured in Unified CM Admin under (User Management > End User or Application User)
0x8CCC005E (2362179678)Directory is unavailable. Verify that the LDAP server is reachable from Unified CM node, make sure that the network connectivity between Unified CM and the LDAP server by pinging the LDAP server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost
0x8CCC00D1 (2362179793)Application is connecting to a non secure port but has security priviledges enabled for the user associated with the application. Check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCC005F (2362179679)Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
0x8CCC00D0 (2362179792)User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCC011D (2362179869)Directory login failed - Password expired. The user's login credentials have expired. The user can change the password by logging into the Cisco Unified CM User Options website using his/her existing credentials. The Cisco Unified CM User Options website will display the logon status indicating that the password has expired and will prompt the user to enter a new password
0x8CCC011F (2362179871)Directory login failed - Account locked. A user has been locked out of his or her account. Lockouts can occur for one of the following reasons: 1) Too many tries: a user made too many login attempts using invalid credentials. Contact the user to confirm that he or she has been attempting to login. You can verify a user's login credential in Cisco Unified CM Administration (User Management > End User/Application User), select the User and click the Edit Credential button, then, under Credential Information, enable the Reset Hack Count checkbox to reset the hack count for this user and clear the Time Locked Due to Failed Login Attempts field. After the counter resets, notify the user that he or she can try logging in again. 2) Account locked by administrator: when warranted, an administrator can lockout a user's access. To do so, go to Cisco Unified CM Administration and click User Management > End User/Application User, select the user and click the Edit Credential button, then . To lock or unlock a user's account, under the Credential Information page, select or deselect the Locked by Administrator checkbox. 3) Account locked due to an extended period of inactivity: the Administrator must notify the user that his or her account has been locked due to inactivity. To unlock the user's account, the Administrator must change the password in Cisco Unified CM Administration by clicking under (User Management > End User/Application User), selecting the User and modifying the password in the End User/Application User Configuration window. After changing the password, notify the user about of his or her new password and encourage the user to change the password in Cisco Unified CM User Options to a new password of the user's choosing

Error Message

%: %[ErrorCode=ULong][SeqNumber=Long][ErrorMessageString=String][AppID=String][ClusterID=String][NodeID=String]: Requested operation from the application has failed.

Explanation   The requested operation from the application could not be performed because of a normal or abnormal condition

Recommended Action   Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation

Error Message

%: %[LoginUserId=String][SeqNumber=Long][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: CTI application connection has been closed.

Explanation   Application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   This alarm is for informational purposes only; no action is required.

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1Heart beat from application missed. Possible causes include network connectivity issues or Unified CM node experiencing high CPU usage. Make sure that the network connectivity between Unified CM and the application by pinging the application server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. Also check for and fix any network issues or high CPU usage on the application server
2Unexpected shutdown; possibly cause is application disconnected the TCP connection. Also check for and fix any network issues or high CPU usage on the application server
3Application requested provider close
4Provider open failure; application could not be initialized
5User deleted. User associated with the application is deleted from the Unified CM Administration
6SuperProvider permission associated with the application is removed. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
7Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
8CAPF information unavailable. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
9Certificate compromised. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
11User is not authorized to connect to CTI using TLS. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
12Standard CTI Use permission removed. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information

Error Message

%: %[LoginUserId=String][SeqNumber=Long][Version=String][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: CTI application connection opened..

Explanation   Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode.

Recommended Action   This alarm is for informational purposes only; no action is required.

Error Message

%: %[CmNodeID=Long][AppID=String][ClusterID=String][NodeID=String]: Unable to communicate with the Cisco CallManager service.

Explanation   CTI cannot communicate with Cisco CallManager service to register supplementary service features

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI heartbeat timed out; application disconnected.

Explanation   CTI heartbeat timeout occurred causing CTIManager to close the application connection

Recommended Action   Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate Expired; Application Disconnected.

Explanation   CTI Peer certificate expired causing CTIManager to close the application connection

Recommended Action   The validity period of the peer certificate used for making SSL connection is expired. Please update the certificate

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate will expire soon; If expired, application will disconnect.

Explanation   CTI Peer certificate expire soon.

Recommended Action   The validity period of the peer certificate used for making SSL connection will expire soon. Please update the new certificate for getting continous service

Error Message

%: %[MsgVersion=VoidPtr][CompatibleVersions=VoidPtr][CurrentVersion=VoidPtr][CMVersion=String][IPAddress=String][IPv6Address=String][AppID=String][ClusterID=String][NodeID=String]: Incompatible protocol version.

Explanation   The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Verify that the correct version of the application is being used. If you're unsure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins)

Error Message

%: %[DeviceName=String][SeqNumber=Long][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIPAddr=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: Device opened.

Explanation   Application opened a device

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DeviceName=String][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIpAddr=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device closed.

Explanation   Application closed a device

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control Center section in Cisco Unified CM Administration (Tools > Control Center - Feature Services)
2Device has unregistered with Cisco Unified Communications Manager
3Device failed to rehome to Cisco Unified Communications Manager; verify that the device is registered
4Device is removed from the Unified CM database
5Application controlling the device has closed the connection
6Route Point already registered by another application
7CTI Port already registered by another application
8CTI Port/Route Point already registered with dyamic port media termination
9Enabling softkey failed for device; verify that the device is registered
10Multiple applications have registered the device with media capability that do not match
11This device is already controlled by another application
12Protocol used by the device is not supported
13Device is restricted for control by any application
14Unable to communicate with database to retrieve device information
15Device is resetting
16Unable to register the device as specified media type is not supported
17Unsuppported device configuration
18Device is being reset
19IPAddress mode does not match what is configured in Unified CM

Error Message

%: %[CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device Open failed.

Explanation   Application is unable to open the device

Recommended Action   Check the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0x8CCC0013 (2362179603)Device is already opened by another application; identify the application that is controlling this device. You can determine this information from RTMT (CallManager->CTI Manager and CallManager->CTI Search)
0x8CCC00DA (2362179802)Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCC009A (2362179738)Device is unregistering; wait for the device to register. Due to user initiated reset or restart of the device from Unified CM. Device should automatically register wait for few moments for the device to register
0x8CCC0018 (2362179608)Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC00F3 (2362179827)IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing mode of the device in Cisco Unified CM Administration (Device > Device Settings > Common Device Configuration)

Error Message

%: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Device is out of service.

Explanation   Device is out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][callManagerId=Long][AppID=String][ClusterID=String][NodeID=String]: Device in service..

Explanation   Device is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[SeqNumber=Long][DirNum=String][Partition=String][DeviceName=String][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line opened.

Explanation   Application opened the line

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[CTIconnectionId=Long][DeviceName=String][DirNum=String][Partition=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Unable to open the line.

Explanation   Application is unable to open the line

Recommended Action   Review the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
0x8CCC0018 (2362179608)Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC0005 (2362179589)Line is not found in the device; possible cause could be that the line that previously existed on this device is not available. This could be due to a extension mobility login or logout
0x8CCC00D3 (2362179795)Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application

Error Message

%: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Line closed..

Explanation   Application closed the line

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1CallManager failure
2Device has unregistered with Cisco Unified Communications Manager; wait for the device to register
3CTI failed to rehome the line; verify that the device is registered
4Undefined line, possible cause could be that line is no more active on that device due to extension mobility login or logout
5Device removed
6Provider controlling the device is closed
7Protocol used by the device is not supported
8Application cannot control this line as CTI Allow Control is not enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application
9Unable to register the device; application specified media type is not supported
10Device is being reset; verify that the device is registered before opening the line
11Unsuppported device configuration

Error Message

%: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Line is out of service.

Explanation   Line is going out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[LineId=Long][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line in service.

Explanation   Line is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DirNum=String][AppID=String][ClusterID=String][NodeID=String]: Error in setting message waiting indicator.

Explanation   An error occurred when setting the message waiting indication (MWI) lamp

Recommended Action   The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI

Error Message

%: %[SeqNumber=Long][DirNum=String][Partition=String][AppID=String][ClusterID=String][NodeID=String]: Request from application to redirect a call has failed.

Explanation   CTIManager is unable to redirect a call

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than allowed.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider

Recommended Action   The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than the limit for each node.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.

Recommended Action   One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTIManager is unable to allow connections from Applications..

Explanation   CTIManager is unable to accept connections from applications

Recommended Action   CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: OutputQbeMessage: length mismatch..

Explanation   QBE header length mismatch exists.

Recommended Action   This alarm indicates that TSP/JTAPI is incompatible with the version of CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset..

Explanation   QBE Packet received from the application is not encoded correctly.

Recommended Action   A TSP/JTAPI interface error occurred; the QBE message may not be formatted correctly. TSP/JTAPI might be incompatible with the version of CTIManager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to register CtiLine with SSAPI..

Explanation   CTI cannot register CtiLine with SSAPI.

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Socket connection has been broken..

Explanation   The TCP connection has been lost.

Recommended Action   Although connection to the application is lost, no action is required if lost connection was intentional. If loss of connectivity was unintentional, investigate what might have caused connectivity to be lost and restore the connection.

Error Message

%: %[SeqNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTI directory login failure..

Explanation   CTI Manager is unable to login to directory. As a result, the application may not be able to access the controlled device list.

Recommended Action   In Cisco Unified CM Administration, verify that the correct username and password has been configured and is being used for CTIManager login. If LDAP is used for authentication, check to confirm that the LDAP synchronization is configured and is working.

Error Message

%: %[LoginUserId=String][DeviceName=String][DeviceType=Long][AppID=String][ClusterID=String][NodeID=String]: DeviceOpenRequest failure..

Explanation   Application is trying to access a device that is not in its control.

Recommended Action   Check the application sending the request or add the device to the user control list.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Illegal QBE header..

Explanation   Because of illegal QBE header, QBE message has been rejected.

Recommended Action   QBE header could be fragmented due to TCP fragmentation. Review your network configuration to fix any TCP fragmentation issue.

Error Message

%: %[SeqNumber=Int][DirNum=String][Partition=String][DeviceName=String][UserName=String][AppID=String][ClusterID=String][NodeID=String]: Line open failed..

Explanation   Application failed to open a line.

Recommended Action   Add the device associated with the line to the user device control list.

Error Message

%: %[EnumHandle=Long][EnumObjectType=String][AppID=String][ClusterID=String][NodeID=String]: Enumeration handle is not valid..

Explanation   The enumeration handle associated with the process of enumerating devices, lines or DNs is invalid.

Recommended Action   Check whether all devices, lines or DNs configured for the application are available to the application. If the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User).

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][QBEMessageLength=Long][AppID=String][ClusterID=String][NodeID=String]: Incoming QBE message exceeds input buffer size.

Explanation   An incoming QBE message exceeds the input buffer size and then gets dropped.

Recommended Action   The size of the QBE packet could exceed the suggested size when the JTAPI/TSP version is not compatible with the version of CTIManager. Contact the application vendor and verify that the application is compatible with the version of Cisco Unified Communications Manager (Unified CM). If the application vendor requests you to, install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[PDU_Number=Long][AppID=String][ClusterID=String][NodeID=String]: TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (QBE packet is dropped).

Explanation   A null TCP handle is preventing the QBE packets to be reported to applications.

Recommended Action   This problem typically happens due to a network connectivity failure. Check for and resolve any connectivity issues in your network.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Directory change notification request time out..

Explanation   CTIManager registration request to EnvProcDevList timed out; CTIManager will send another registration request.

Recommended Action   Check and resolve network connectivity problems between Cisco Unified Communications Manager nodes.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MYTCP_Send: send error..

Explanation   TCP socket connection has been broken.

Recommended Action   This problem occurs when an application is abruptly shut down or has lost network connectivity to CTIManager. Review your application and network connectivity and resolve any issues.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to create an internal process that is required to service CTI applications..

Explanation   An unexpected internal SDL error caused a failure in creating CTIManager Service SDL Process.

Recommended Action   An internal CTIManager error has occurred. Try Restarting the CTIManager service to resolve this problem, if it does resolve the problem restart the Unified CM Server.

Error Message

%: %[ErrorCode=Int][AppID=String][ClusterID=String][NodeID=String]: CTIManager service is unable to initialize TCP connection.

Explanation   CTIManager service is unable to initialize TCP connection

Recommended Action   CTIManager has encountered difficulty initializing TCP connections. Restart the CTIManager service to resolve this problem.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ProviderOpenRequest; illegal filter size..

Explanation   ProviderOpenRequest has an illegal filter size.

Recommended Action   The application is using an incompatible version of JTAPI/TSP and Cisco Unified Communications Manager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI NewCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI ExistingCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating response to application request for call information..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: Connection handle is not valid..

Explanation   A message has been received from an unknown connection, and then dropped.

Recommended Action   This alarm occurs when a QBE packet is received from a connection that is already disconnected. This packet will be ignored by CTIManager and no action is required.

Error Message

%: %[UserNameSize=Long][AppID=String][ClusterID=String][NodeID=String]: Invalid userName size in ProviderOpen request..

Explanation   User name length is invalid.

Recommended Action   Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters.

Error Message

%: %[AdditionalInfo=String][AppID=String][ClusterID=String][NodeID=String]: Database connection failed..

Explanation   An attempt to connect to database failed.

Recommended Action   Enable trace for the database layer monitor to get specific error information.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: No database connection available..

Explanation   Database layer could not find any working database connection.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully..

Explanation   Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.

Recommended Action   At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Could not read installed RPMs to populate component version table.

Explanation   The function that reads the rpm version information and populates database failed

Recommended Action   Please report this error to the administrator.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client was responding slowly and has been removed..

Explanation   A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.

Recommended Action   Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification shared memory reconciliation has occurred..

Explanation   The change notification buffers in shared memory have been rebuilt due to conflicts.

Recommended Action   This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Indicates debug events from IDS database engine..

Explanation   This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.

Recommended Action   This is for debug information purposes only; no action is required.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: No error has occurred but some routine event completed in IDS database engine..

Explanation   This alarm is informational. No error has occurred but some routine event completed in IDS database engine.

Recommended Action   This is for information purposes only; no action is required.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Pay Attention. This alarm does not compromise data or prevent the use of the system..

Explanation   Pay Attention. This alarm does not compromise data or prevent the use of the system.

Recommended Action   This alarm needs monitoring by the db admin

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail.

Explanation   This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail

Recommended Action   Requires db admin intervention

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Information about IDS replication.

Explanation   This alarm provides information about IDS replication.

Recommended Action   Informational purposes only; no action is required

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. IDS Replication has failed.

Explanation   This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication

Recommended Action   Requires db admin intervention

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for Integration, CUP import files has failed.

Explanation   Combined alarm for Integration, CUP import files has failed

Recommended Action   Check the network and files in the CUP server

Error Message

%: %[user=String][AppID=String][ClusterID=String][NodeID=String]: An application or endpoint is using too many database resources.

Explanation   This alarm indicates an error situation. Resources are not exhausted. The application will not be granted more connections to the database until the ones used are freed up.

Recommended Action   Collect the trace using file get activelog cm/trace/dbl/sdi/limitexceeded*.tar.gz or by collecting the Cisco Database Layer Monitor trace in RTMT to determine the application or endpoint causing issues.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Out of memory..

Explanation   The process has requested memory from the operating system, and there was not enough memory available.

Recommended Action   No action is required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Permission has been denied..

Explanation   An operation could not be completed because the process did not have authority to perform it.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service is not installed..

Explanation   An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.

Recommended Action   Reinstall the service.

Error Message

%: %[IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: Service stopped..

Explanation   A service has stopped.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ProcessID=ULong][IPAddress=String][IPV6Address=String][Hostname=String][ServiceName=String][VersionInfo=String][AppID=String][ClusterID=String][NodeID=String]: Service started..

Explanation   A service has started.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service startup failure..

Explanation   An attempt to start the specified service failed.

Recommended Action   Restart the service.

Error Message

%: %[PrimaryFilePath=String][AppID=String][ClusterID=String][NodeID=String]: Cannot write into a file..

Explanation   Failed to write into the primary file path.

Recommended Action   Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Error reading enterprise default user locale configuration.

Explanation   A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.

Recommended Action   Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN stream ICMP port unreachable error..

Explanation   An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ANN device record not found..

Explanation   A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.

Recommended Action   To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: WAV playing manager thread creation failed.

Explanation   The process component used for playing WAV files failed to start, possibly due to low system resources.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: ANN device recovery create failure..

Explanation   The ANN device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Enterprisewide configuration exception.

Explanation   An unknown exception occured reading Enterjprisewide configuration settings.

Recommended Action   Verify the enterprise configuration settings and restart the IP Media Streaming Service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown Configuration Exception.

Explanation   An exception error was generated reading the service parameter settings.

Recommended Action   Restart the server.

Error Message

%: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: Configuration COM Exception.

Explanation   A COM exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%: %[Description=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Configuration DBL Exception.

Explanation   An exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: ANN device configuration not found.

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.

Recommended Action   Review the service parameter settings and configure the ANN device settings properly using the CUCM Administration.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN requested streams failure..

Explanation   The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value shown as "Allocated" is non-zero

Recommended Action   Verify the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.

Error Message

%: %[Error=ULong][ErrorText=String][Path=String][AppID=String][ClusterID=String][NodeID=String]: ANN create local path error.

Explanation   Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.

Recommended Action   Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP event wait error.

Explanation   An error was reported while waiting for a list of events. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service. If the error continues, restart the serverr.

Error Message

%: %[ExceptionCode=ULong][AXReg=ULong][BXReg=ULong][CXReg=ULong][DXReg=ULong][SIReg=ULong][DIReg=ULong][IPReg=ULong][SPReg=ULong][BPReg=ULong][Flags=ULong][CSSeg=ULong][DSSeg=ULong][ESSeg=ULong][SSSeg=ULong][FSSeg=ULong][GSSeg=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer exception failure.

Explanation   An unknown program exception has caused the background TFTP file transfer processing for announcement files to terminate. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.

Error Message

%: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer thread creation failed.

Explanation   The ANN background TFTP file transfer processing thread failed to create possibly due to low system resources.

Recommended Action   Reboot server.

Error Message

%: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP COM exception.

Explanation   A COM exception occured while processing the specified file.

Recommended Action   Review the file for possible format errors or missing elements.

Error Message

%: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML parsing error.

Explanation   There is a syntax error in the specified file.

Recommended Action   Correct the syntax error.

Error Message

%: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML invalid element .

Explanation   There is an invalid element in the specified file.

Recommended Action   Correct the error.

Error Message

%: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP file missing.

Explanation   A file was not found on the TFTP server to be downloaded to the announcement server.

Recommended Action   Correct the error.

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: TFTP start file transfer failed.

Explanation   Unable to start transfering a file from TFTP server.

Recommended Action   Verify the file name exists on the TFTP server.

Error Message

%: %[TFTPServer=String][AppID=String][ClusterID=String][NodeID=String]: Unable to create TFTP client.

Explanation   Unable to create a client TFTP session with the TFTP server.. This may be due to the server not running, or an incorrect server name configuration setting in service paramenters. This operation will be retried periodically.

Recommended Action   Verify the TFTP server is operating and configuration settings are correct.

Error Message

%: %[Error=ULong][ErrorText=String][FileName=String][AppID=String][ClusterID=String][NodeID=String]: Open announcement file failed.

Explanation   An error was reported when attempting to open an announcement file for reading.

Recommended Action   Verify the file exists and the Cisco IP Voice Media Streaming App service has proper access rights to open the file for reading.

Error Message

%: %[LocaleID=ULong][Type=String][AppID=String][ClusterID=String][NodeID=String]: Unknown ANN Locale.

Explanation   The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.

Recommended Action   Install the locale package or check device settings for an incorrect locale value.

Error Message

%: %[Locale=ULong][AnnID=ULong][AppID=String][ClusterID=String][NodeID=String]: Requested announcement not found.

Explanation   The requested announcement is unknown. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the CUCM Admin to view a list of custom announcement identifiers and verify the correct one is being used.

Recommended Action   Correct the announcement identifier chosen from the custom announcement list.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: CFB device recovery create failure..

Explanation   The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[MohAudioSourceFileName=String][MohAudioSourceId=UInt][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Music On Hold Audio Source file cannot be opened.

Explanation   This alarm occurs when Music On Hold fails because the MOH audio source file cannot be opened. The caller will hear silence instead of the desired Music on Hold audio.

Recommended Action   Use the CUCM Administration interface for "MOH Audio File Management" on this specific MOH CUCM server to check that the Music On Hold Audio Source file has been uploaded to this specific server. Note that MOH audio files must be uploaded using the CUCM Administration page of each MOH server in the cluster before that server can play the audio file. If you need to upload the file you will need to reset this MOH device after the upload so it will be accessable by the MOH device.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CFB device record not found..

Explanation   A device record for the software conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.

Recommended Action   To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: CFB device configuration not found..

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.

Recommended Action   Review the service parameter settings and configure the CFB device settings properly using the CUCM Administration.

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB stream ICMP error..

Explanation   A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification subsystem not starting..

Explanation   The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Invalid notification event returned by database change notification..

Explanation   The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.

Recommended Action   Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurances.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification restart failure..

Explanation   The change notification subsystem failed to restart.

Recommended Action   This service has change notification disabled, it may be reenabled at a later time or restart Cisco IP Voice Media Streaming App service to reenable immediately.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creating audio source class failed..

Explanation   Unable to create audio source subcombonent to provide audio for streaming. This may be due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Stream Control create failure..

Explanation   Create stream control subcomponent. The error may possibly be due to lack of memory.

Recommended Action   Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: IP TOS MediaResource to Cm value not found..

Explanation   The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP (011000).

Recommended Action   Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.

Error Message

%: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming device driver error..

Explanation   The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.

Recommended Action   Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.

Error Message

%: %[DeviceName=String][ServerNumber=ULong][ServerName=String][AppID=String][ClusterID=String][NodeID=String]: Device connection manager failed to start..

Explanation   The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of device manager exit event failed..

Explanation   An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.

Recommended Action   This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager in lockout..

Explanation   The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to CUCM is being suspended. This will cause a switch to another CUCM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the CUCM server.

Recommended Action   Check the status of the Cisco Unified Communications Manager service. You may have to restart the CUCM service or the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: More than 50 events returned from TCP link..

Explanation   The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.

Recommended Action   No action is required. Monitor for reoccurance. This could be an indication of a security issue.

Error Message

%: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Open receive failure..

Explanation   The open receive channel failed. This may indicate a missmatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance monitor counters for resource availability on CUCM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager not responding..

Explanation   The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with CUCM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with CUCM.

Recommended Action   Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of CUCM. The media device should automatically reregister.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Registered with Cisco Unified Communications Manager..

Explanation   The software media device registered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Connection error with Cisco Unified Communications Manager..

Explanation   The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.

Recommended Action   No action is required. The media device will reregister.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Create driver notification event failure..

Explanation   An error was returned when creating a signaling event for communication with the media streaming kernel driver. This may be due to memory or system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation socket event failure..

Explanation   An error was reported when creating a notification event for a socket interface. This may be due to a resource shortage. The media device will remain unavailable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurance or restart the CUCM server.

Error Message

%: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Start transmission failure..

Explanation   An error was encountered while starting an RTP transmission audio stream. This may indicate a missmatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance counters for the media resources on CUCM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.

Error Message

%: %[TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in device manager thread..

Explanation   An error was reported during a system request to wait on an event, the media device will be restarted.

Recommended Action   No action is required.

Error Message

%: %[DeviceName=String][TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of thread failure..

Explanation   An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server to recover from this error.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Unregister with Cisco Unified Communications Manager..

Explanation   A media device has unregistered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required. The media device will automatically reregister.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed MOH stream control failed to start..

Explanation   The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.

Recommended Action   Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface failed to start..

Explanation   An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.

Recommended Action   Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface initialization failure..

Explanation   Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.

Recommended Action   Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additionsl information.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input codec stream initialization failure..

Explanation   Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.

Recommended Action   Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input audio stream transcoder failure..

Explanation   An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.

Recommended Action   Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Get audio source file name failure..

Explanation   The Music-on-Hold audio source is not assigned to an audio file.

Recommended Action   Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco IP voice media streaming driver not found..

Explanation   The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.

Recommended Action   Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of required signaling event failed..

Explanation   An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.

Recommended Action   Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Error while waiting for asynchronous notifications of events..

Explanation   An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).

Recommended Action   Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the local host server name..

Explanation   Unable to obtain the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.

Recommended Action   Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the network IP address for host server..

Explanation   Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of the IPVMSMgr thread failed..

Explanation   An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.

Error Message

%: %[Found=ULong][Need=ULong][AppID=String][ClusterID=String][NodeID=String]: Wrong version of device driver..

Explanation   An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.

Error Message

%: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming application starting..

Explanation   The Cisco IP Voice Media Streaming App service is starting.

Recommended Action   No action is required.

Error Message

%: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: The IP voice media streaming application shutting down..

Explanation   The Cisco IP Voice Media Streaming App service is shutting down.

Recommended Action   No action is required.

Error Message

%: %[AudioSourceID=ULong][ConferenceID=ULong][CodecType=String][IPAddress=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: Invalid multicast IP address..

Explanation   An invalid multicast IP address (out of range) was found.

Recommended Action   Correct the setting on the Music-on-Hold device configuration for multicast address.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH device record not found..

Explanation   A Music-on-Hold device was not found for this server. This device is normally automatically added when a server is added to the configuration.

Recommended Action   If Music-on-Hold functionality is required, you will need to remove and readd server to the database. WARNING: This may impact many other configuration settings (CM Groups, Media Resource Groups, etc...).

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH stream ICMP error..

Explanation   A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Error starting MOH Audio source subcomponent..

Explanation   A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of MOH manager exit event failed..

Explanation   An error was encountered when allocating a signaling event. This may be caused by a resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Synchronization error detected in MOH audio manager..

Explanation   A synchronization error was detected. Condition has been resolved automatically.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in MOH manager thread..

Explanation   An error was encountered in Music-on-Hold audio manager subcomponent while waiting for aynchronous event signaling. The MOH device will be restarted.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Starting of MOH audio manager failed..

Explanation   An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Attempted to rewind an inactive MOH audio source..

Explanation   An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.

Recommended Action   No action required.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Error rewinding MOH audio source that is not playing..

Explanation   An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.

Recommended Action   No action is required.

Error Message

%: %[ErrorText=String][File=String][SrcPath=String][DstPath=String][OSError=Int][OSErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Transfer of MOH source file to working path failed..

Explanation   An error was encountered when trying to copy or update a Music-on-Hold audio source file.

Recommended Action   Use the Platform CLI to verify the source path and file exist. If the file does not exist then use CUCMAdmin to reupload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MTP device record not found..

Explanation   A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.

Recommended Action   If MTP functionality is required, you will need to delete the server and re-add the server back to the database using CCMAdmin. WARNING: This may require many additional configuration settings to be reapplied such as CallManager Groups, Media Resource groups and more.

Error Message

%: %[CallCount=ULong][RunFlag=String][AppID=String][ClusterID=String][NodeID=String]: MTP device configuration not found, starting with defaults..

Explanation   One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.

Recommended Action   Configure the service parameter settings for the MTP device.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Get change notification port failure..

Explanation   The database layer was unable to find change notification port and is using default.

Recommended Action   If default change notification is incorrect or change notification does not work, add value into database and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Database layer select my process node failed..

Explanation   The database layer was unable to find/determine the current node on which this service is running.

Recommended Action   Make sure the database is configured properly.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH enabled codecs not found..

Explanation   The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G.711 mu-law codec.

Recommended Action   Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.

Error Message

%: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read clsterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%: %[ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while tring to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH TFTP IP address not found..

Explanation   The default MOH TFTP IP address was not found in the database.

Recommended Action   Audio sources may be unavailable; create proper value in database and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB requested streams failure..

Explanation   The resources for the number of requested full-duplex streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH requested streams failure..

Explanation   The resources for the number of requested streams was not available.

Recommended Action   Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MTP requested streams failure..

Explanation   The resources for the number of requested full-duplex Media Termination Point streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MOH device recovery create failure..

Explanation   An error was encountered restarting the Music-on-Hold device. This may be caused by a shortage of memory resources.

Recommended Action   Check the status of the Music-on-Hold device. If the MOH device is not registered and available, Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MTP device recovery create failure..

Explanation   An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.

Recommended Action   Restart the IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Invalid Software License..

Explanation   There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.

Recommended Action   Install a valid software license and restart Cisco IP Voice Media Streaming App service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Valid Software License Found..

Explanation   A valid software license has been detected by the IP Voice Media Streaming App service.

Recommended Action   No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.

Error Message

%: %[Filename=String][AnnouncementID=ULong][UserLocale=ULong][NetworkLocale=ULong][AppID=String][ClusterID=String][NodeID=String]: Announcement file not found..

Explanation   The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.

Recommended Action   Upload the custom announcement to the server or install the missing locale package.

Error Message

%: %[Devicename=String][AppID=String][ClusterID=String][NodeID=String]: Failed to initialize sRTP crypto..

Explanation   The media device shown in this alarm attempted to load and initialize crypto capabilities within the operating system kernel, however, a failure, such as the OS lacking encryption configuration, a memory shortage, or crypto self-test failure, occurred during initialization. Secure media encryption for this device has been disabled as a result, but unencrypted media is still supported. All media streams are non-secure (unencrypted) for this device. This alarm is capable of occurring when the crypto failure occurs because the Cisco IP Voice Media Streaming App service parameter Force Annunciator to be Non-secure or Force MOH to be Non-secure is enabled.

Recommended Action   Use the Cisco Unified Real-Time Monitoring Tool (RTMT) to retrieve the system log. Review the system log and respond to error messages containing sRTP or IpVms.

Error Message

%: %[ReasonCode=ULong][Identifier=String][Locale=String][AnnouncementEnum=ULong][FileName=String][CustomFileName=String][AppID=String][ClusterID=String][NodeID=String]: Unable to play a requested announcement or tone.

Explanation   Reason code explanations: [1] Announcement requested is undefined. The announcement enum number is unknown. [2] Locale requested is unknown. The requested locale has not been installed on this node. [3] The customized announcement file does not exist on this server node for the locale. If a default system announcement is assigned, it will be used in place of the customized announcement. [4] Internal annunciator resource shortage has caused the announcement to fail. [5] System announcement or tone file not found.

Recommended Action   Recommendations based on reason code: [1] this is usually a system design issue and cannot be resolved by normal means; [2] Be sure the requested locale is installed on each CUCM server node; [3] Upload the customized announcement wav file to this server node using CCM Administration on this node; [4] Review the annunciator device configuration for maximum number of calls and/or schedule an annunciator device reset as a temporary workaround to ensure orphanned resources are released or restart the Cisco IP Voice Media Streaming App service; [5] Check locale is installed on CUCM server node or possible missing file not installed properly.

Error Message

%: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create a new thread. See Reason string for where it failed..

Explanation   This usually happens when there are system issues such as running out of memory resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to update trace logging or alarm subsystem for new settings..

Explanation   This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TFTP service and database trace files.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to build all device configuration files at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to start listening to configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes in Cisco Unified Communications Manager Group settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes at group level settings such as Device Pool or Common Device Config settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught in the main processing routine..

Explanation   This alarm is sent in conjunction with other alarms for failure when building configuration files or when the TFTP service is attempting to retrieve the values in the system's enterprise parameters.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught while retrieving enterprise parameters value from database at TFTP service startup..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database when rebuilding all configuration files..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A complete rebuild of all device configuration files has failed..

Explanation   Probable causes of this alarm could be failure to access the Cisco Unified Communications Manager database, or misconfiguration of some devices.

Recommended Action   In Cisco Unified Serviceability, enabled Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[nError=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to open network connection for receiving file requests..

Explanation   This usually happens when the IP address that the TFTP service uses to open the network connection is invalid.

Recommended Action   Verify that the TFTP service parameter, TFTP IP Address, accurately specifies the IP address of the NIC card to use for serving files via TFTP. See the help for the (advanced) TFTP IP Address service parameter for more information. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Failed to increase the size of the network buffer for receiving file requests..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Fail to connect to the network port through which file requests are received..

Explanation   This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TFTP server.

Recommended Action   Verify that the port is not in use by other application. After stopping the TFTP server, at the command line interface (CLI) on the TFTP server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: No Cisco Unified Communications Manager (Unified CM, formerly known as Cisco Unified CallManager) node has been configured..

Explanation   A Cisco Unified Communications Manager Group exists but it has no Unified CM node configured as its group member.

Recommended Action   In Cisco Unified CM Administration (System > Cisco Unified CM Group), configure at least one Unified CM node for the Unified CM Group referenced in this alarm. The Unified CM Group is part of the device pool to which the specified phone belongs.

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create Config File on disk or update existing Config File on disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to save Config File to disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[ErrorNumber=Int][FileName=String][IPAddress_Port=String][Mode=String][OpCode=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: There was an error during processing of file request..

Explanation   This could happen if the requested file is not found by the server, or other error indicated by the "Reason" clause when processing the file request.

Recommended Action   You can safely ignore this alarm if the reason shown in this alarm is "File not found" and if that file is the MAC address-based file name for a phone that you are auto-registering; in that case, the phone is not yet registered with the database and so it is normal for the phone's file not be found. In the case that auto-registration is disabled, this alarm shows that the phone or device is not added to Cisco Unified Communications Manager (Unified CM). Either add the phone to Unified CM or remove the phone from the network. If you still get this error after removing the phone(s), go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception was caught while processing file request..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[DeviceCount=Int][DeviceTime=Int][UnitCount=Int][UnitTime=Int][SoftkeyCount=Int][SoftkeyTime=Int][FeatureControlPolicyTime=Int][FeatureControlPolicyCount=Int][DialruleCount=Int][DialruleTime=Int][TotalTime=Int][BuildStatus=String][AppID=String][ClusterID=String][NodeID=String]: Device configuration files are being built..

Explanation   This alarm provides information about the BUILD ALL operation to build all types of configuration files.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: IPv6 network interface is not installed..

Explanation   IPv6 option is enabled for TFTP service but the IPv6 network interface/address has not been configured on the system. Until the IPv6 network is functioning, devices that have been configured with IPv6-only will not be able to register. Devices that have been configured to use either IPv6 or IPv4 will register using IPv4. When the IPv6 network is online, IPv6-capable devices that have registered as IPv4 will remain IPv4 until they are reset, at which time they will use IPv6 if available.

Recommended Action   Install IPv6 network interface and then restart TFTP service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ITL file regeneration.

Explanation   This is for regeneration of ITLFile

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: The IP Address for host was NOT RESOLVED.

Explanation   The IP Address for host was NOT RESOLVED

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There are no CallManager entries in the database..

Explanation   There are no CallManager entries in the database.

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was timeout during wait for DeActivateLoadShare acknowledgement.

Explanation   There was timeout during wait for DeActivateLoadShare acknowledgement

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the LineStateSrvEng Creation.

Explanation   There was an error during the LineStateSrvEng Creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the GlobalSPUtils creation.

Explanation   There was an error during the GlobalSPUtils creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TapiLinesTable creation.

Explanation   There was an error during the TapiLinesTable creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the HuntGroupController creation.

Explanation   There was an error during the HuntGroupController creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the Hunt Group creation.

Explanation   There was an error during the Hunt Group creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the CallDirector creation.

Explanation   There was an error during the CallDirector creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SysController creation.

Explanation   There was an error during the SysController creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TimerServices creation.

Explanation   There was an error during the TimerServices creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: DBL GetVersionInfo function returned NULL.

Explanation   DBL GetVersionInfo function returned NULL

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Exception occured in InitSDIConfiguration function.

Explanation   Exception occured in InitSDIConfiguration function

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SyncDB creation in SysController.

Explanation   There was an error during the SyncDB creation in SysController

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Connection to CallManager was lost.

Explanation   Connection to CallManager was lost

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User successfully logged in..

Explanation   User successfully logged in.

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User log in failed because of bad user id or password..

Explanation   User log in failed because of bad user id or password.

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User is already logged in.

Explanation   User is already logged in

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User logged out.

Explanation   User logged out

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Agent online.

Explanation   Agent online

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Agent offline.

Explanation   Agent offline

Recommended Action   NONE

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[Userid=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: User is not Synced.

Explanation   While updating the data in db for User Db gave exception

Recommended Action   Check the reason for exception and proceed accordingly.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application error.

Explanation   IPMA application error

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Manager Logged out.

Explanation   IPMA Manager Logged out by application

Recommended Action   To re-login the user, click update in the CCMAdmin IPMA Service configuration page for this user.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application overloaded.

Explanation   IPMA application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application filtering is down.

Explanation   IPMA Application filtering is down

Recommended Action   Restart Cisco IP Manager Assistant Service

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Information .

Explanation   Application information

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application error.

Explanation   BDI application error

Recommended Action   See application logs for details

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application overloaded.

Explanation   BDI application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to startup WebDialer application.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application error.

Explanation   WebDialer application error

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application overloaded.

Explanation   WebDialer application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer informational alarm.

Explanation   WebDialer application informational alarm

Recommended Action   No action required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSync Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSymc application failed to start successfully.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error, may require restarting the application

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process started on particular sync agreement.

Explanation   LDAPSync process started to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to start on particular sync agreement.

Explanation   LDAPSync process failed to start on the configured agreement id

Recommended Action   See application logs for error

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process completed on particular sync agreement.

Explanation   LDAPSync process completed to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped manually on particular sync agreement.

Explanation   LDAPSync process stopped manually on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped automatically on particular sync agreement.

Explanation   LDAPSync process stopped automatically on the configured agreement id, it will be restarted automatically

Recommended Action   No action required

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   No action required. The sync process will automatic retry See application logs for details

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   See application logs for details, the application will try to sync again in the next scheduled time

Error Message

%: %[AgreementId=String][LDAPHost=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to connect to LDAP server.

Explanation   LDAPSync process failed to connect to LDAP host

Recommended Action   Please make sure the LDAP server is online. If SSL is used, please make sure the required certificate is available on local CM server. The application will automatically retry

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to access local database.

Explanation   CiscoDirSync failed to access local database

Recommended Action

Unable to connect to vpn using openwrt, what to do?

Have a router with openwrt firmware 15.05 and access to the Internet via PPPoE (DS). You need to connect via vpn to play in the toy, but does not work.
What they do:
Install package ppp-mod-pptp
Create pptp interface, configure, maintain
Trying to raise it, but no response...

What to do in this situation? In openwrt and nix, I'm a noob. Tried to Google, but something is not went...

/etc/config/network
/etc/ppp/options.pptp

log after clicking Connect:

Thu Mar 17 07:43:03 daemon 2016.notice netifd: Interface 'test22' is now down
Thu Mar 17 07:43:03 daemon 2016.notice netifd: Interface 'test22' is setting up now
Thu Mar 17 07:43:03 2016 daemon.info pppd[2794]: Plugin pptp.so loaded.
Thu Mar 17 07:43:03 2016 daemon.info pppd[2794]: PPTP plugin version 1.00
Thu Mar 17 07:43:03 daemon 2016.notice pppd[2794]: pppd 2.4.7 started by root, uid 0
Thu Mar 17 07:44:00 daemon 2016.warn pppd[2667]: connect: Connection timed out
Thu Mar 17 07:44:00 daemon 2016.err pppd[2667]: Could not open control connection to 31.214.241.206
Thu Mar 17 07:44:00 2016 daemon.info pppd[2667]: Exit.
Thu Mar 17 07:45:06 daemon 2016.warn pppd[2749]: connect: Connection timed out
Thu Mar 17 07:45:06 daemon 2016.err pppd[2749]: Could not open control connection to 31.214.241.206
Thu Mar 17 07:45:06 2016 daemon.info pppd[2749]: Exit.
Thu Mar 17 07:45:10 2016 daemon.warn pppd[2795]: connect: Connection timed out
Thu Mar 17 07:45:10 2016 daemon.err pppd[2795]: Could not open control connection to 31.214.241.206
Thu Mar 17 07:45:10 2016 daemon.info pppd[2795]: Exit.
Thu Mar 17 07:45:10 2016 daemon.err pppd[2794]: Call manager exited with error 256
Thu Mar 17 07:45:10 2016 daemon.info pppd[2794]: Exit.

Olaf.Kilba asked July 15th 19 at 23:50

More answers about "Unable to connect to vpn using openwrt, what to do?"

1 answer

Looks like I picked a very good vendor... I Tried a few others - earned

Please sign in or sign up to write your answer or comment.

Find more questions by tags Network administrationVPN

grep pppd

Code:

Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pppd[2316]: pppd 2.4.7 started by root, uid 0 Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pppd[2316]: Using interface ppp0 Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pppd[2316]: Connect: ppp0 <--> /dev/pts/5 Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pppd[2316]: LCP: timeout sending Config-Requests Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pppd[2316]: Connection terminated. Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pppd[2316]: Modem hangup Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2320]: anon warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pppd[2316]: Using interface ppp0 Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pppd[2316]: Connect: ppp0 <--> /dev/pts/6

tail -f /var/log/syslog

pptp client on Linux: Disable crazy anon logging (callmgr)


When I needed to transfer some data to an offsite using a PPTP VPN, I followed these two tutorials to get the connection running on my Debian Wheezy server:

  • http://websistent.com/how-to-configure-a-linux-pptp-vpn-client/
  • http://www.vionblog.com/debian-pptp-client-configuration/

Basically the steps are the following.

Install pptp client:

apt-get install pptp-linux

Then enter the vpn credentials in /etc/ppp/chap-secrets:

myvpnuser      PPTP      myvpnpass     *

Then create a new config file for the VPN connection in the /etc/ppp/peers folder. Here I used vpnconn1 as name (/etc/ppp/peers/vpnconn1):

pty "pptp ip.address.remote.site --nolaunchpppd"
name myvpnuser
remotename PPTP
require-mppe-128
file /etc/ppp/options.pptp
maxfail 0
persist
ipparam vpnconn1

pty: The command line options to launch the pptp client and therefore the connection. ip.address.remote.site is of course the IP address or DNS Name of the VPN Server.

name: It's the username again, which must be the same as defined in chap-secrets.

ipparam: Use the same naming again, as your vpn connection (vpnconn1)

After that I manually launched the VPN connection with the following command:

pppd call smartdev

In /var/log/syslog the following entries appeared:

Jul 21 11:27:01 irnsrvp01 pppd[117523]: pppd 2.4.5 started by root, uid 0
Jul 21 11:27:01 irnsrvp01 pppd[117523]: Using interface ppp0
Jul 21 11:27:01 irnsrvp01 pppd[117523]: Connect: ppp0 <--> /dev/pts/57
Jul 21 11:27:01 irnsrvp01 pptp[117527]: anon log[main:pptp.c:314]: The synchronous pptp option is NOT activated
Jul 21 11:27:01 irnsrvp01 pptp[117553]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
Jul 21 11:27:01 irnsrvp01 pptp[117553]: anon log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
Jul 21 11:27:01 irnsrvp01 pptp[117553]: anon log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
Jul 21 11:27:02 irnsrvp01 pptp[117553]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Jul 21 11:27:02 irnsrvp01 pptp[117553]: anon log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
Jul 21 11:27:02 irnsrvp01 pptp[117553]: anon log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 1640).
Jul 21 11:27:06 irnsrvp01 pppd[117523]: CHAP authentication succeeded
Jul 21 11:27:06 irnsrvp01 pppd[117523]: MPPE 128-bit stateless compression enabled
Jul 21 11:27:09 irnsrvp01 pppd[117523]: local  IP address 10.0.0.11
Jul 21 11:27:09 irnsrvp01 pppd[117523]: remote IP address 10.0.0.10

Success! The VPN connection was established. 

But then the crazyness started! Several times per second I got such log entries:

Jul 21 11:31:14 irnsrvp01 pptp[98247]: anon fatal[open_callmgr:pptp.c:487]: Call manager exited with error 256
Jul 21 11:31:14 irnsrvp01 pptp[98259]: anon log[main:pptp.c:314]: The synchronous pptp option is NOT activated
Jul 21 11:31:14 irnsrvp01 pptp[98260]: anon warn[open_inetsock:pptp_callmgr.c:329]: connect: Connection refused
Jul 21 11:31:14 irnsrvp01 pptp[98260]: anon fatal[callmgr_main:pptp_callmgr.c:127]: Could not open control connection to ip.address.remote.site

Altogether pptp logged more than 99k lines into /var/log/syslog. Now if you use OSSEC on that server, and I do, then you can imagine how many alert e-mails you get. I stopped counting after the 1500th alert e-mail.

The question now is: How can I tell pptp to stop logging? Eventually I found a very old (from 12 years ago!) mailing list post in which a command line parameter is mentioned (--loglevel):

should allow you to reduce the verbosity of logging by adding the option "--loglevel 0" to your pptp command line.

As I described above, the command line options are actually defined in the VPN connection's config file (/etc/ppp/peers/vpnconn1) in the "pty" line.

# cat /etc/ppp/peers/vpnconn1
pty "pptp ip.address.remote.site --nolaunchpppd --loglevel 0"
name myvpnuser
remotename PPTP
require-mppe-128
file /etc/ppp/options.pptp
maxfail 0
persist
ipparam vpnconn1

By adding the "--loglevel 0" option into that line, the crazy logging stopped and only a few "Echo Reply received" entries appeared from time to time.


Add a comment

Show form to leave a comment

Comments (newest first)

No comments yet.

grep pptp

Code:

Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pptp[2320]: anon log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 2 21:55:42 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 2 21:55:43 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 2 21:55:43 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 2 21:55:43 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 48985, peer's call ID 1244). Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2320]: anon warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2320]: anon warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled) Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 12 'Call-Clear-Request' Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[call_callback:pptp_callmgr.c:84]: Closing connection (call state) Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2343]: anon log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 2 21:56:14 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 2 21:56:14 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 2 21:56:14 rpr-HP-ProBook-430-G4 pptp[2356]: anon log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 18349, peer's call ID 1245).
tail -f /var/log/ppp-connect-errors

Code:

anon fatal[open_callmgr:pptp.c:525]: Call manager exited with error 256 anon warn[open_unixsock:pptp_callmgr.c:383]: bind: Address already in use anon fatal[callmgr_main:pptp_callmgr.c:136]: Could not open unix socket for 84.22.27.96 anon fatal[open_callmgr:pptp.c:525]: Call manager exited with error 256 anon warn[open_unixsock:pptp_callmgr.c:383]: bind: Address already in use anon fatal[callmgr_main:pptp_callmgr.c:136]: Could not open unix socket for 84.22.27.96 anon fatal[open_callmgr:pptp.c:525]: Call manager exited with error 256 anon warn[open_unixsock:pptp_callmgr.c:383]: bind: Address already in use anon fatal[callmgr_main:pptp_callmgr.c:136]: Could not open unix socket for 84.22.27.96 anon fatal[open_callmgr:pptp.c:525]: Call manager exited with error 256
The same log when connection was working:
tail -f /var/log/ppp-connect-errors

Code:

anon warn[open_unixsock:pptp_callmgr.c:374]: Call manager for 84.22.27.96 is already running. anon fatal[callmgr_main:pptp_callmgr.c:136]: Could not open unix socket for 84.22.27.96 anon fatal[open_callmgr:pptp.c:526]: Call manager exited with error 256 anon warn[open_unixsock:pptp_callmgr.c:374]: Call manager for 84.22.27.96 is already running. anon fatal[callmgr_main:pptp_callmgr.c:136]: Could not open unix socket for 84.22.27.96 anon fatal[open_callmgr:pptp.c:526]: Call manager exited with error 256
I think this line is the error but i don't know it means:
Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2320]: anon warn[decaps_hdlcptp_gre.c:226]: short read (-1): Input/output error
Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2320]: anon warn[decaps_hdlcptp_gre.c:238]: pppd may have shutdown, see pppd log
Jan 2 21:56:13 rpr-HP-ProBook-430-G4 pptp[2334]: anon log[callmgr_mainptp_callmgr.c:245]: Closing connection (unhandled)


Any help will be appreciated.
Thank you