Problem | Indicates that the SIP Proxy has successfully started. |
User response | None. |
Problem | Indicates that the SIP Proxy has terminated normally. |
User response | None. |
Problem | We can not connect to the address |
User response | None. |
Problem | Transport Error, unable to send message to target. |
User response | None. |
Problem | Indicates that an outbound connection to a client was successful. |
User response | None. |
Problem | Indicates that a new inbound connection from a client was successful. |
User response | None. |
Problem | A connection to a client has been broken. |
User response | None. |
Problem | The SIP Proxy Server has made a successful connection to a SIP Container. |
User response | None. |
Problem | A connection to a SIP Container has been broken. This may be caused by a container going down, but could also be caused by a network device or networking timeout in the operating system. If it is not a container outage, it is likely the connection will be recreated and this message can be ignored. |
User response | Check that the container is still up and running. If not, restart it. If so, then no action is required as the connection will be recreated automatically. |
Problem | An attempt to connect to a client failed. |
User response | None. |
Problem | An attempt to connect to a server failed. |
User response | None. |
Problem | The SIP Proxy did not find any associated channel chains. |
User response | None. |
Problem | The SIP Proxy received a start quiesce request. |
User response | None. |
Problem | The SIP Proxy quiesce is completed. |
User response | None. |