The device did not respond to an INVITE or REGISTER Both the terminals and the telephone gateways can be contacted for the normal functioning of the system, by sending SIP, INVITE and / or REGISTER requests. If the device does not respond to a first request, subsequent requests are sent, because the single packet could […]
Read More
A terminal or gateway has failed authentication. When there are terminals and / or telephone gateways that register on UCloud, the system operates as a SIP server. The device sends a first request in clear text, i.e. without authentication credentials. REGISTER sip: acme.ucloud: 5142 SIP / 2.0 … From: <sip: 301@acme.ucloud: 5142>; tag = 3148eb62c3 […]
Read More
Description of the problem: When using a VoIP operator (carrier) who authenticates through registration credentials (username and password), the UCloud server behaves like a SIP client, sending REGISTER packets to the operator: REGISTER sip: sip.niceprovider.it SIP / 2.0 Via: SIP / 2.0 / UDP 81.82.83.84:5142;rport;branch=z9hG4bK147B044C2 From: <sip: 0234567890@sip.niceprovider.it>; tag = 73EB1459 To: <sip: 0234567890@sip.niceprovider.it> Expires: […]
Read More
The remote device behind the NAT (terminal / gateway) within the same session has changed the source IP / Port. If the duration of the UDP NAT sessions is configured correctly, i.e. greater than the registration period, each device will send a request before the NAT session expires which therefore will never change. Each device […]
Read More
The recording period set on the device is less than 60 seconds. The cause and the solution are simple. An incorrect period has been set and must be reset with a value between 60 and 120 seconds. Note that some terminals express the recording period in seconds (most of them) and others in minutes (Grandstream […]
Read More
The UI fails to establish the connection SSE (server-sent events) The UI uses a permanent connection with the http protocol to receive notifications about the status of calls, users and gateways. The port used varies for each company and is indicated in the company configuration as “http port”. Possible causes: The firewall / antivirus of […]
Read More
The call_manager received a response to an INVITE after at least 4 retransmissions It is a mitigated version of the Unreachable Device case and could occur together with it, due to too short NAT sessions on the router. Normally each invite should receive a 100 Trying response within a few milliseconds of sending. If the […]
Read More
In a call with a gateway, the gateway call received less than a third of the rtp packets sent. In peer to peer (p2p) calls between terminals and telephone gateways, the system cannot detect any anomalies on voice / video traffic, since this traffic remains confined to the local network. Conversely, calls to and from […]
Read More
The UI registration has expired. Periodically, each UI sends an update request from the active registration on the server (login refresh) and the system checks that this request arrives on schedule. Possible causes: There was an interruption in the network connection, for the same reasons explained in the Terminal or gateway registration timeout paragraph. Reasonably, […]
Read More
The pbx received a clear request (INVITE \ REGISTER) and sent only one 401 (authentication challenge) after which nothing more arrived from the remote device. Possible causes: Although quite rare, there are terminals that do not support authentication via username and password. These terminals, once they receive a negative response with a 401, do not […]
Read More
