Check feature availability on Rainbow client
Once the WebRTC Gateway, PBX Sip trunk and Virtual resources (REX on OmniPCX Enterprise, AnyDevice on OXO Connect and OXO Connect Evolution) are configured and your main phone is well associated to your Rainbow account you should have in your Rainbow client new menu to select your call routing.
In this call routing menu you can now choose your device to make phone calls. The devices list depends of wich phone numbers you have defined into your profile, default entries are Office Phone if you have a deskphone, Computer (internet calls) and Other phone.
Configuration, Status and connectivity check
Reminder: Use the command mphelp to obtain a list of all the commands and their explanations. SSH access is deactivated by default. If you need to activate/deactivate it you have to run following commands: mpssh ON|OFF
Configuration
The command mpshow will display the current configuration used by the WebRTC gateway.
Status
The command mpstatus will display the current status of the different services running on the WebRTC gateway.
You can restart the WebRTC gateway with the mprestart command; This will restart all services.
You can reboot the WebRTC gateway with the mpreboot command.
Connectivity
The command mpcheck will execute some connection tests to Rainbow cloud. The Network configuration and the access to NTP, DNS, Proxy, PBX, TURN server are checked.
The command mpcollect --all will save in addition to the mpcheck results some information about the WebRTC gateway (HW, CPU/RAM usage, installed linux packages, running services, etc...) and the WebRTC gateway logs. The resulting output file is located by default in $HOME/mpcollect.tgz
At the request of the support team, you may need to change the logging level before reproducing a problem and collecting logs. This is done with the mplog command, option debug or verbose. After reproducing the problem, reset the level to info. Once you modify the level, you'll have to restart the gateway with the mprestart command (no reboot required, just a restart).
The currently configured log level can be checked with the mpshow command.
Please provide this mpcollect.tgz file when you open a support request.
SIP traces with the mpndump command
Since version 2.3.7 it is recommended to use the command mpndump (on|off|clean) to make sip traces.
When mpndump is run, the command checks whether there is enough disk space to generate a maximum of 8 files of 32 MB each, with a file rotation mechanism. For the disk space check, an additional margin of 512 MB is taken into account to reserve space for a remote upgrade.
In conclusion, a minimum of 768 MB of free disk space is required to start capturing with mpndump.
Files will be saved to $HOME/rainbow/ with following format ndump-2023-10-06T06-57:04.pcap-0 up to pcap-7.
When the mpndump command starts old files are first removed.
Note that you can close the ssh console, the tcpdump trace capture will not be stopped. When reconnecting you'll see that the tcpdump is still running, To stop the trace capture you'll have to run the command mpndump off.
Please provide the files pcap-0 to 7 when you open a support request.
Once you have collected the files you can remove them with the command mpndump clean.