Jump to content

syukri

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

syukri's Achievements

Apprentice

Apprentice (3/14)

  • One Year In Rare
  • Collaborator Rare
  • One Month Later Rare
  • Week One Done Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. I have updated the PBX to the newest v69.2 and tested the webRTC trunk call. I still got the same result as the previous version (69.1.x). I found a tool in Chrome to analyze the webRTC call connection, chrome://webrtc-internals. Attached is the snapshot of the result when i initiate call connection using webRTC Call button from browser to the PBX. Honestyly i'm not proficient in troubleshooting webRTC connection as this thing is new to me. hopefully someone can guide me to find the source of failure and fix this issue.
  2. so you are saying in your test environment, the call using webRTC trunk is successful? i need to wait for the next release to test again the webRTC trunk is it?
  3. It can ring the destination ext but the call not connected properly as when i pickup the call from the ext, nothing can be heard. From the webRTC button side (Chrome browser), when i click the button Make Call (green), it does not turn to End Call (red) when ringing the destination ext. i notice the indicator of the page using microphone (red blinking dot besides the tab) appear when i tried making call using webRTC button.
  4. Hi, i have issue with webRTC Talk Button after upgrade my pbx to V69.1.4 from V68 where it can only ring the destination but cannot connect between 2 parties. At first i thought this issue was related to different build (V69 vs V68), but then i tried downgrade the V69.1.4 to V69.0.8 and the webRTC call button can straigh away ringging the destination and complete the call between 2 parties. so it makes me believe it either the V69.1 have issue with webRTC or my configuration on the pbx/trunk might need to be updated after upgrading to that version. i tried to do packet capture from the caller side but found nothing on the wireshark. what i can see is only some error inside chrome's inspect elements. Anyone have idea on what i need to configure to make the call button using webRTC works for V69.1.4 or help to find the thing that couse the problem. Attached is the picture of error i found from Chrome. If using V69.0 and bellow, i can click the Call now button and it will turn red and ring the destination and the call can connected between 2 parties. For V69.1.4, when click on the Call now button, it stays green but ringging the destination ext. when answer the call, the called party unable to hear the calling party.
  5. Ouh, is that so. But in my environment, i am able to login to app using classroom extension.
  6. for Classroom type extension, did they have the ability to manually change the DnD status from their login? for example in Android Apps or Desktop App.
  7. is this under the individual ext setting? I did try several other things but still no luck for me. Is this also related to Group permission?
  8. Hi, did anyone tried automatic DnD based on service flag for Classroom type extension in V69? I try to use the function on 1 of my extension but it done nothing. I set the extension as Classroom, then under Redirection tab, i set the Classroom DnD control to use my service flag. I set both for manual and automatic service flag, when it active, it doesn't turn on DnD for that extension. is this the expected result for this current version is my setting is the problem? I'm using the latest version of V69.0.4
  9. Is this command can use in Windows Server as my PBX is running on Windows Environment? I have an issue where the prev password cannot be used to login as admin after update to this version.
  10. Hello. I'm having some issues with Vodia IoP device. This device is come with 64gb micro SD card which contains the OS and PBX inside. This device was used by another person before me. The issues i'm having are: During my first try to boot the device by connecting the usb for power, it does blink the lights at the network port which was a good news according to manual. it means the device is trying to obtain an ip address from DHCP and it got 1 (checked from the router). I tried to ping the ip and got the replies back. i tried to navigate using the link provided at the box to find the device but unfortunately the device not showed up. i tred to browse using it's ip address to see if i could bring up the vodia interface but failed. According to manual, i only need to enter the provided url to bring up the interface. simple as that but its not working. can anyone that familiar with this to explain/give any idea on how to rectify this. Since I unable to bring up the interface, i tried to check for the logs in the OS. To do that i plug in the micro SD card to SD card reader and insert into my windows laptop which i run linux on VM. I mistakenly mount the micro SD card to my windows env. I tried to open the micro SD card to see the content inside but system show error massage (ofcourse since windows files system not match with the linux). to see the log, i mount the micro SD card to my vm running linux. i am able to take a look at logs. in the boot logs, it only end until 26 jan but i did tried to power up the device on 27th and 28th. it shows the system does not boot at all into the OS after i put the micro SD card into card reader and connect to my computer to see the content inside. I need advice on how to fix this. Thank you
  11. Hi, I'm posting this issue here as i really need help in figuring out the cause of this issue. PBX version is 68.0.18, installed in Debian 10. the problem expected to start when a user reported that there are missed calls dated on 1/1/1970 in the vodia desktop app. At that time we though it was just a callback made by the PBX for each missed calls since the log entries seemingly match with the missed calls that happened during that day. I never check the recording files in the server at this point, but the recorded calls start to corrupt on the same day user noticed the weird missed call on 1/1/1970. The problem was expected to be solved by upgrading the system to latest version which is .26. 2 weeks later i try to update the system but the process failed. I had tried to install from version .20 until .26, but all were unsuccessful. The process is stuck at (4/6) then it shows the update is failed. Then I restart the pbx service in the hoping the update will be successful after that. Suddenly the service stopped and unable to restart from the server itself. The whole pbx was down and cannot be access through url anymore. i decided to do fresh installation of vodia in the server and backup the old directories.
  12. In Window app, there are 2 locations to set Call Forwarding which are, using arrow button next to DnD and under Settings-> Call Forwarding. Are both of these settings serves the same purpose or they have different functions? As i noticed, only setting for call forwarding using arrow button is working while the one under Settings does not work. If they have the same purpose, i think better just remove the one that does not work as it may rise confusion
  13. thank you for the support. it helps clear the confusion.
  14. Hi, is there any way for me to mark/flag a certain answer/topic as solved/answered/helpful? IMO, this feature will certainly help anyone who trying to find answers regarding vodia in this forum.
  15. Does anyone know where is the recorded call for scheduled conference is located? I have check the logfile and recorded call in pbx but no recording for the schedule conference that i made. For the ad-hoc conference setup, the recording is available in recorded call. i also have check under each extension that i included as participant in that schedule conference, and yet no recording for the particular conference. Please help.
×
×
  • Create New...