HP VCX Software IPsec key negotiations, Starting SIP TCP server at port, Stopped SIP TCP server

Appendix B. Troubleshooting

Starting SIP TCP server at port 5060

This message will be shown when the SIP module is started. This can happen when you apply settings where the SIP module just has been activated, or when you boot the Telecom- muting Module or after you have pressed the Restart the SIP module button on the Restart page. It means that the Telecommuting Module is now ready to receive SIP signaling over TCP.

Starting SIP UDP server at port 5060

This message will be shown when the SIP module is started. This can happen when you apply settings where the SIP module just has been activated, or when you boot the Telecom- muting Module or after you have pressed the Restart the SIP module button on the Restart page. It means that the Telecommuting Module is now ready to receive SIP signaling over UDP.

Stopped SIP TCP server

This message will be shown when the SIP module is stopped. This can happen when you ap- ply settings where the SIP module just has been deactivated, or when you boot the Telecom- muting Module or after you have pressed the Restart the SIP module button on the Restart page. It means that the Telecommuting Module can no longer receive SIP signaling over TCP.

Stopped SIP UDP server

This message will be shown when the SIP module is stopped. This can happen when you ap- ply settings where the SIP module just has been deactivated, or when you boot the Telecom- muting Module or after you have pressed the Restart the SIP module button on the Restart page. It means that the Telecommuting Module can no longer receive SIP signaling over UDP.

IPsec key negotiations

These log messages can appear when the IPsec key negotiations box has been checked on the Display Log page.

IPsec: "<peer name>-<tunnel number>" #<event number>: ignoring informational payload, type <payload type>

The IPsec peer <peer name> sent a message during negotiation which the Telecommuting Module ignores, because it can’t use it. The payload type (like IPSEC_RESPONDER_LIFETIME) will give you a hint about what is the matter. The event number is a counter for how many negotiation attempts has been performed for this peer.

IPsec: "<peer name>-<tunnel number>" <IP address> #<event

number>: Issuer CRL not found

The Telecommuting Module has no Certification Revocation List for the CA of the peer’s certificate. This is not an error, but is perfectly normal. You only need a Certification Revo- cation List when you want to make some certificates invalid.

333