Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Today
  2. Looks to me like the PBX could not open the sockets for HTTP/HTTPS. Maybe the firewall does not like the new executable? What OS is that? Check with netstat is the ports were opened.
  3. Every phone has a different place to enter the SIP password for an account. Generally I would recommend to use the automatic provisioning for VoIP phones. There are many other settings that should be set, it is very difficult to do that manually. And the PBX is automatically assigning a password to the VoIP phone which is different from the SIP password (every extension has many passwords).
  4. Can you try with http://localhost/rawlogin
  5. I understand that it is essential to activate the DMZ etc. ... on the firewall with the IP address of the server Vodia. I'll try and update you tnx Damiano
  6. Hi, Maybe this will help you understnad better: https://doc.vodia.com/admin_sip_and_audio Look (Ctrl + F) for the word "SIP IP Replacement List" on here.
  7. sincerely I don't understand where to insert my public ip in the parameters of the Vodia, can you kindly indicate me the path where to insert my public ip (example 33.33.33.33) and where to insert the local ip range (in my case 192.168.1.0/24)? Thank you in advance, Damiano
  8. You don't need STUN. The SBC does take care about this. Please see https://doc.vodia.com/server_behind_nat for some basic information about how to run a server behind NAT - this is called "near end" SBC.
  9. I'm sorry, but I can't get my public ip on Vodia. I did the NAT of the RTP range and ports 5060 and 5061 on my firewall to the local ip of the Vodia but the remote phones (with STUN active) are recorded but there is no audio. Probably I miss to insert Public IP on Vodia and what else? my local range is 192.168.1.1/24 and Public IP is 33.33.33.33 (example) where I enter these values correctly, I looked at the documents online but honestly I did not understand much
  10. Had no problem in test server but after upgrading our production system to 63.0 we lost access to the web interface! Tried from various IPs, from same LAN and from localhost with no success. Ports 8080 and 443 are open and LISTENing, we get connected but then the pbxctrl gives zero bytes back. I'm providing the ouput of tests from localhost with wget and openssl below. Please help as soon as possible. wget -vvvv http://localhost:8080/ --2019-05-24 13:40:19-- http://localhost:8080/ Resolving localhost (localhost)... ::1, ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:8080... connected. HTTP request sent, awaiting response... No data received. Retrying. [...same error again and again...] wget -vvvv https://localhost --2019-05-24 13:28:21-- https://localhost/ Resolving localhost (localhost)... ::1, ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:443... connected. Unable to establish SSL connection. openssl s_client -debug -host localhost -port 443 CONNECTED(00000003) write to 0x21d3500 [0x21d3580] (289 bytes => 289 (0x121)) 0000 - 16 03 01 01 1c 01 00 01-18 03 03 58 2a 59 35 05 ...........X*Y5. 0010 - 31 9e c9 3a 58 b9 82 80-ad 03 9c ee cf 4b 2a 1a 1..:X........K*. 0020 - ed 50 8c 11 cf 2b 4a 98-bd be 24 00 00 ac c0 30 .P...+J...$....0 0030 - c0 2c c0 28 c0 24 c0 14-c0 0a 00 a5 00 a3 00 a1 .,.(.$.......... 0040 - 00 9f 00 6b 00 6a 00 69-00 68 00 39 00 38 00 37 ...k.j.i.h.9.8.7 0050 - 00 36 00 88 00 87 00 86-00 85 c0 32 c0 2e c0 2a .6.........2...* 0060 - c0 26 c0 0f c0 05 00 9d-00 3d 00 35 00 84 c0 2f .&.......=.5.../ 0070 - c0 2b c0 27 c0 23 c0 13-c0 09 00 a4 00 a2 00 a0 .+.'.#.......... 0080 - 00 9e 00 67 00 40 00 3f-00 3e 00 33 00 32 00 31 ...g.@.?.>.3.2.1 0090 - 00 30 00 9a 00 99 00 98-00 97 00 45 00 44 00 43 .0.........E.D.C 00a0 - 00 42 c0 31 c0 2d c0 29-c0 25 c0 0e c0 04 00 9c .B.1.-.).%...... 00b0 - 00 3c 00 2f 00 96 00 41-c0 12 c0 08 00 16 00 13 .<./...A........ 00c0 - 00 10 00 0d c0 0d c0 03-00 0a 00 07 c0 11 c0 07 ................ 00d0 - c0 0c c0 02 00 05 00 04-00 ff 01 00 00 43 00 0b .............C.. 00e0 - 00 04 03 00 01 02 00 0a-00 0a 00 08 00 17 00 19 ................ 00f0 - 00 18 00 16 00 23 00 00-00 0d 00 20 00 1e 06 01 .....#..... .... 0100 - 06 02 06 03 05 01 05 02-05 03 04 01 04 02 04 03 ................ 0110 - 03 01 03 02 03 03 02 01-02 02 02 03 00 0f 00 01 ................ 0120 - 01 . read from 0x21d3500 [0x21d8ae0] (7 bytes => 0 (0x0)) 140427521087376:error:140790E5:SSL routines:ssl23_write:ssl handshake failure:s23_lib.c:177: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 289 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None Krb5 Principal: None PSK identity: None PSK identity hint: None Start Time: 1558694617 Timeout : 300 (sec) Verify return code: 0 (ok) ---
  11. on the GDPR I know the problem, in any case I see how to change the pswd SIP (so I change it without knowing the previous one), the question remains on how to enter via the web to the phone, where is the place to insert it? Maybe I don't see where to put it?
  12. You would have to enter a new password. In the IT world it is generally a bad idea to show passwords. It might be even against GDPR to show e.g. a user password to the administrator. Look at all the news about facebook leaking passwords!
  13. I have not changed absolutely nothing except that, but in computer science everything is possible
  14. System management DNS address has nothing to do with NTP. Maybe the problem went away because of some other change.
  15. with reference to the SIP pswd of the extension and the web access to the phone I can not understand how to read them. Let me explain, in case of provigioning for example of a Snom/Grandstream phone or other, the phone is registered to the Vodia Server. If, for any reason, I have to enter via web from the phone or manually register the phone, how can I go back to the credentials of the extension, considering that they are not visible?
  16. hi, in reality I think I have solved by setting "System management DNS address", since I put in this field I DNS the error of the NTP has been solved. Correct doing so? Damiano
  17. Grandstream has a lot of different devices, with a lot of different firmware and a lot of different settings names ("Pxxx"). For the LAN provisioning maybe there is something different with their web server. We will have to check this here. The solution is to log into the web interface of the phone and manually set the address of the PBX (see https://doc.vodia.com/pnp_grandstream) in the setting "Config Server Path" - and make sure that the extension 203 is opened for MAC-based provisioning.
  18. NTP does not tell the phone what time zone it is in. This is done using the phone provisioning. For setting the NTP server, there are two things you can do here. Pick a NTP port (e.g. 8232) so that the PBX will provide the NTP service (not sure but this might require a restart of the PBX service) and then re-provision the phone. Obviously then you must make sure that the PBX has the correct time. Or make sure that the phone can reach the NTP server on public Internet. You can also choose another server, e.g. pool.ntp.org. Maybe your firewall is blocking that kind of traffic. You can also check on the phone if it was able to resolve the DNS address (snom phones show you the content of the DNS server).
  19. Bye, despite having set up the NTP server (see 3 attached screens) the SNOM-715 phone displays the attached information at each boot. Solution?
  20. hi, I tried to supply Grandstream phone (GXP1625 FW 1.0.4.132) but it was impossible. Vodia sees the phone (I attach a screen) but you can not supply it. I tried several times to make a format factory of the phone and to press the key on Vodia but nothing happens. Solution?
  21. Yesterday
  22. The above setting should be on the /reg_pnp_settings.htm page of the Admin level PBX GUI.
  23. When you provision the phone for the first time, it sets the address for the PBX - including the port number. If you change the port number, well, it will become unavailable. What you can do is to keep the old port open (e.g. use "8080 80" in the HTTP port settings). You can change the templates from the web interface (/reg_texts.htm): You can do this on system, domain and extension level. But usually you don't have to do that, just set the general parameter for the phones (reg_pnpparm.htm). When you change buttons the PBX automatically sends a re-provision request to the phone. You can manually trigger that by going to the registration tab for the extension (dom_ext3.htm) and there click on the re-provision or the reboot button for the registration.
  24. Hi, I'm on vodia V63 with debian 9.9. I found a bug in the provisioning. If you change http or https port from standard port 80 or 443 provisioning stop to working correctly. In my case i provisioned a Snom 710 with standard port 80. Then i change http port to 8090. Deleted mac address bid to extension, reset the phone. This result in provisioning fault. Restoring port http 80 all start to working good. I think this is a possible bug. Then I install new clean PBX: i do same test changing http port to 8090 directly before provisioning: same result: provisioning fail. This is my fisrt problem. Second problem is that i need to modify standard provisioning template to change phone standard beahaviour for some parameters. Were are located in a linux debian environment .xml provisioning files ? I search in all folders under usr/local/pbx without result. Last question is about reprovisioning phones. I cannot find command to send reprovisioning command in case we need to change BLF or bottoms. Thank you in advance Matteo
  25. What you could try to do is to set the "Label template for private lines" from "{user} {name}" to "", so that the label sent to the phone is empty:
  1. Load more activity
×
×
  • Create New...