Click “Debug” icon in the upper menu, tick off “Debug dialplan” and click “Save”.
Now the logs of the calls are saved and you can see the log of each call:
14.3. Trace generation
WMS Settings > Tools and utilities > Generate trace
This tool allows generation of a *pcap trace that helps you to debug and analyze eventual problems with VoIP traffic on the PBX or on separate interfaces.
DOCUMENTATION:
Pcap trace generation guide: https://manuals.wildix.com/wms-settings/#trace
WP4X0 reset and recovery: Press the central button of the Navigation keys and hold it for several seconds.
Enable remote syslog on Wildix devices: WMS > Devices, double click on a provisioned device to edit it and select “Syslog Server” (enter the address of the remote server).
ISDN gateways:
Access the media gateway web interface System menu > Syslog and activate “Diagnostic Traces”
Connect to the media gateway via SSH (on Windows you can use “putty” or other SSH clients) using the same credentials you used for access to web interface
Type “logs on” (at the end of the session, type “logs off”)
Make a test call
The logs help you to understand eventual issues, here is what happens when a user places an outgoing call to a trunk:
PBX receives a request from the user and forwards it to the BRI/PRI gateway
The gateway forwards the call to the operator
The operator responds to the gateway with the status “Call Proceeding” to confirm the reception of the request
The operator responds with the status “Call Progress” to indicate that the call has been routed to the destination
The operator responds with the status “Alerting” to indicate that the destination is available
The operator responds with the status “Setup Confirm” to indicate that the call has been responded
In case the call could not be connected or the call was hang up by the operator, the media gateway receives the following message: “Unicast RECV Disconnect”
Check the field indicating the reason of the call disconnection, for example: “Cause: Normal call clearing (16)”. Check the codes of disconnection reasons: http://www.cnes.com/causecodes.html
14.5. Other
Upper menu > “info”: Monit service allows you to check the performance of the system services, CPU, memory usage.
Upper menu > “ports block”: check if any ports needed for remote trunks and calls are not open
Appendix 7: Ports to open for Wildix services
Remote support, upgrades, auto-configuration via auto.wildixin.com
Make sure that Firewalls that limit the Internet access to the PBX, allow the traffic to wmp.wildix.com and vpn2.wildix.com on the 443 TCP and 1194 UDP ports
WMS network
Enable the port 443 TCP (or another custom secure port) and 1194 UDP on the side of the Master PBX
Remote provisioning of devices
Incoming ports:
443 TCP (default) or another external secure port (SIP-RTP page);
5060 UDP - 5061 TCP for SIP registration
RTP ports: from 10000 to 15000 (SIP-RTP page)
SIP Trunks registration
Outgoing ports:
5060 UDP or another custom port specified in trunk settings
Collaboration and Web Phone
443 TCP (default) or another external secure port (SIP-RTP page);
RTP ports: from 10000 to 15000 (SIP-RTP page)
iOS/Android
SIP: 5061/TLS, if blocked 443/TLS
XMPP: 443 TCP for Android; 5223 TCP for iOS, if blocked 443 TCP
Configuration: 443 TCP
Custom secure port (SIP-RTP page): add manually on the app login page: Account > Domain, example: pbx.wildixin.com:443 (for iOS works only with public IP)
RTP ports: from 10000 to 15000 (SIP-RTP page)
WebRTC Kite service
Outgoing ports:
Incoming ports:
RTP ports: from 10000 to 15000 (SIP-RTP page)
WebRTC Kite Video conference
Open the port 443 TCP (default) on a firewall towards:
conference.wildix.com
ws2sip.wildix.com
videobridge.wildix.com
turn.wildix.com
Share with your friends: |