The asynchronous communication mechanism between the PBX and the web configurator often means that the configurations saved by the administrator and sent by the configurator to the PBX are not acknowledged at the very moment of the administrator’s confirmation as one or more modified entities are currently in use by the system. . In this […]
Read More
In the Monitoring–> Parking Lines section, you can monitor the status of the PBX’s parking lines. The information shown is as follows: Line code Numeric code associated with the parking line Number Number of the parked interlocutor Name Name of the parked interlocutor Status Line status: free / busy Last operation Date / time of […]
Read More
In this section you can view the status of meeting rooms in progress, ie meeting rooms whose deadline has not yet passed. Here you can therefore see both the rooms with active interlocutors, and halls with no interlocutors. Meaning of the Columns: Internal: internal number associated with the meeting room Name: Name of the room Date […]
Read More
In questa sezione è possibile effettuare un’analisi avanzata delle chiamate gestite dal centralino VOIspeed
Read More
This section shows the voice messages received in the company mailboxes of the PBX (excluding the users’ personal mailboxes). The information shown in this section is as follows: Voicemail Name of the voicemail Date time Date and time of the call Duration Duration of the recording Author Number of the caller Status New () Listened […]
Read More
This section of the configurator contains a simple report of the calls made / received by the VOIspeed PBX. The list is obtained without any particular advanced criteria, but thanks to the possibility of sorting the individual fields of the table, it allows you to have a complete picture of the switchboard activity. Table legend: […]
Read More
The VOIspeed switchboard allows you to systematically record both incoming and outgoing calls without the voluntary intervention of users or a voicemail box. The default registration status is disabled, and can be enabled in each individual routing rule by configuring the relevant functionality in the GDPR panel (see GDPR Panel – Reporting). Recordings of this […]
Read More
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
