Jump to content

netpro78

Members
  • Posts

    79
  • Joined

  • Last visited

Everything posted by netpro78

  1. In version 58.2 I am happy to see that CSV import is back, however it seems to force certain fields. In the old version I could pre-populate items like park orbits, and disable mailboxes. It seems like all of that functionality is now lost, and only certain fields are accepted. I used to use the following format that now does not seem possible: type,alias,ani,password,web_pass,first_name,display_name,mb_pin,mb_enable,picom,orbits
  2. Upon further testing the no audio from the WebRTC issue seems to be related to Firefox. Using Google Chrome has no issues.
  3. It does generate a user disconnects call log whaen I attempt it. The interesting thing is it does not seem like it receives any packets: Packets (Tx/Rx): 1429 0 Codec (Tx/Rx): PCMU/8000 Address: 79.146.173.76 SDP-State (Local/Remote): sendrecv sendrecv Sequence-Number (Tx/Rx): 47351 32768 User-Agent: Vodia WebRTC 1.0 Call-Quality: VQSessionReport: CallTerm LocalMetrics: Timestamps:START=2015-08-26T22:20:01Z STOP=2015-08-26T22:20:25Z CallID:c1abf8a7@pbx FromID:103@dev.testdomain.local;tag=gu8701 ToID:6443393@dev.testdomain.local;tag=6f7d20647a SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FO=0 FPP=1 PPS=50 PLC=3 LocalAddr:IP=0.0.0.0 PORT=51788 SSRC=0x097b6f4a RemoteAddr:IP=0.0.0.0 PORT=0 SSRC=0x x-UserAgent:Vodia-PBX/5.2.6 x-SIPterm:SDC=OK In the PBX log I am also seeing: [6] 17:20:40.250 WEBS: Delete HTTP connection 8864 [3] 17:20:40.772 SIP: Could not send on socket 127.0.0.1:12345
  4. I was active back through the PBXnSIP 3.4 days, and was happy with the product back then, and lost interest when it started getting tailored for Snom only. Now that it is no longer a Snom product, I decided to revisit it to see what has been fixed, what is still an issue, and what is new. I did a fairly basic demo with the free version to evaluate if I should purchase or not. The following are some issues I see with the current product. I know that some are easy fixes, and some are far more complicated. I am hoping that some could be addressed to make it a worth while purchase. In the event that I did purchase and I wanted to migrate from PBXnSIP 3.4 is there still a migration path, since I see some posts saying the older versions have been removed? Issues that still exist from 3.4 -The service is single threaded -BLF's often show a ringing state when a call is answered with a pickup (*87) -No support for BLA, or SCA -Call sequence numbers get out of order when restarting the pbx for maintenance causing BLFs to stop functioning until the phones are rebooted (this is a killer when trying to run the switch for hosting) New issues I ran across during the demo -You can only add one extension at a time, unless you want to jump through the hoops of creating a CSV file -Certain situations can get a call stuck in the system, and clicking the X next to the call will not remove it -If the "Ignore Packets that do not match the Domain" is selected, then the phones can only place calls. When they attempt to receive calls, they continue to ring since the PBX ignores the SIP signaling from the phones saying that the phone is trying to answer the call. -You cannot create trunks in Firefox -No audio when calling from the web interface -Include cell phone for web callback creates a call between the cellphone, and desk phone, not the cell phone, and the called number.
×
×
  • Create New...