Clearly, the industry is moving to a Burger King state of mind (as in "have it your way").
If all the above solution can't solve your issue, please provide us the trace file for future analysis,trace file including pcap file, config bin and syslog file, and we need three of them provide at one time.Well, I am not going to debate about preferences on IP phone clients. if the issue still exist, then do a hard reset to the base, the steps are below：Ģ) long press the paging key on the base and not stop until step3 is finishedģ) connect the power to base, waiting for the three lights on the base light up one by one, during the whole process, please keep pressing the paging key !Ĥ) after the three lights all light up, release the paging key and reconnect the power supply reset the base and handset to factory and test againģ. To solve this issue, please refer to the steps below :ġ.check if the base and handset of the W52 are the newest or not, if no, please upgrade the firmware first, firmware download link :Ģ.
The caller (intern) can hear the called person (extern). The caller (intern) can not hear the called person (extern).įor checking the freePBX setting I tried to use a X-lite Softphone at the same extension, the w52p is normally bound to.
The called person (extern) can hear the caller (intern). The caller does not have a ring tone at the handset, but the external phone is ringing. When I make a call with the w52p there is the following situation The caller (extern) can hear the called person (intern). The called person (intern) can hear the caller (extern). When a call comes in to the w52p everyting is ok.
There is no switching from simple_bridge to native_rdp. The workaround with ",t" at the end of a dial command is set. I am using the yealink w52p with a freePBX (Asterisk 13.1) installation and Endpointmanager.
0 kommentar(er)
