mskenderian

I am not sure I understand you. Let me clarify a few items, this PBX is not production. I do have a few devices provisioned to it for testing purposes. But this IP geolocates to florida. which i have no customers on the east coast. Regardless of the fact the PBX needs to accept the connection, why am i still getting email notifications? I got 191 emails in the last 8 days for this particular IP.

Below is the logs from the PBX. [8] 9:09:51.135 Accept connection from blacklisted address 192.240.110.202:50788 for 1000 msⓘ [6] 9:09:52.136 Delete SIP connection 3352 from 192.240.110.202:50788ⓘ [7] 9:09:52.136 Connection from 192.240.110.202:50788 closedⓘ

upgraded a small pbx from .16 to .20, no issues.

yes that would indeed be the correct way. but i am. see below. 2nd line shows my entry that i blocked the connection. 1st line shows the PBX auto blocked it for me and i got a notification this particular machine is running 68.0.16 about to upgrade to .20 this week.

the logs i get from from the carrier, just saw that, hard to run distinguish which is which. ending in "@pbx" isnt good, why not hostname or IP? but i think i can also use x-tag for better mapping of which pbx.

No, two different companies, BulkVS.com

I get notifications for ips that get blacklisted, in recents weeks i am getting more and more. specially from the same IP. We started blocking these IPs, but even though the IP is blocked, we still get notifications from that specific IP. anyway to disable these notification if the IP is already blacklisted?

yes I did that, I found settings to control from, to and other items, but Call-ID is a unique string that represents that particular call. it ends in "@pbx" which make it difficult to figure out which PBX it came from.

We want to play a message one time, before transferring to a ring group. I didnt see an option for that, so I guess the work around would be to make a Auto Attendant. I want to play the Message once then send to a ring group. there is a setting named: Number of times to repeat the welcome message Options are Default, 1, 2, 3, 4, 5 There is no 0 option. choosing one will play the message and then repeat the message one time. choosing default plays the message a few times. I did the "Christian Hack", press F12, change the values to 0 then save. this doesnt work. can we add an option for that? Also can we have an option to disable Extension input. i dont want them to be able to get anywhere but listen to the message then transfer to a ring group.

Can we get support for BulkVS SMS?

How can we change the Call ID in the sip messages, INVITE sip: Via: SIP/2.0/TCP From: To: Call-ID: d0b3386a@pbx I would want to send either {unique_call_id}@{pbx_name} OR {unique_call_id}@{pbx_ip_address}

Figured it out. Solution: I disabled IPv6 and it worked. even though i had enabled both ipv4 and ipv6, there was an issue with the server. I dont know why this would have happened, it should nativily work with both IPv4 and IPv6, but we dont need ipv6

ok i also tried to install the newest version, same issue. I started a new VPS, same issue, i have install vodia many times no issues, i dont know what is going on. /usr/local/pbx/pbxctrl --no-daemon --log 9 Starting up [1] 20220817144343: Starting up version 68.0.18 [7] 20220817144343: Checked recording timestamps [7] 20220817144343: Found Interface lo with IP 127.0.0.1/255.0.0.0 [7] 20220817144343: Found Interface enp1s0 with IP 45.32.86.29/255.255.252.0 [1] 20220817144343: Adding DNS server 108.61.10.10 to the dns server list [1] 20220817144343: Adding DNS server [2001:19f0:300:1704::6] to the dns server list [7] 20220817144343: Loaded wakeup list [7] 20220817144343: Loaded certificates [7] 20220817144343: Refreshed license [7] 20220817144343: Loaded buttons [8] 20220817144343: Scheduler precision is 0 us [1] 20220817144343: Working Directory is /root [5] 20220817144343: Starting threads [7] 20220817144343: Found Interface lo with IP 127.0.0.1/255.0.0.0 [7] 20220817144343: Found Interface enp1s0 with IP 45.32.86.29/255.255.252.0 [8] 20220817144343: No from address for sending text email [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:80 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:80 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:443 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:443 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:2345 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:2345 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:2346 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:2346 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:5060 [5] 20220817144343: Set scheduling priority to 1 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:5060 [5] 20220817144343: Set process affinity to 1 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:5061 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:5061 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:161 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:161 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:514 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:514 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:5060 [4] 20220817144343: Join multicast group on address 0.0.0.0 [8] 20220817144343: Joined multicast group 224.0.1.75 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:5060 [7] 20220817144343: UDP (IPv4): Opening broadcast socket on 67 [7] 20220817144343: UDP (IPv4): Opening socket on 127.0.0.1 [7] 20220817144343: Last message repeated 2 times [7] 20220817144343: UDP (IPv6): Opening socket on [::] [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0 [7] 20220817144343: UDP (IPv6): Opening socket on [::] above is the output, i dont see anything wrong. can someone help me figure this out,

I am trying to migrate a server from ubuntu to debian. Install Debian, used vodia script to install. change the install script to use the same version and the current running PBX. which is 68.0. tried (it failed.): VERSION=68.0.0 tried (success): VERSION=68.0 but now it wont start, tried: /etc/init.d/pbx restart output: Shutting down PBX daemon: Starting PBX daemon sudo netstat -tulpn | grep LISTEN tcp 0 0 0.0.0.0:5061 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:2345 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:2346 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1808/sshd: /usr/sbi tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1122/exim4 tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:5060 0.0.0.0:* LISTEN 42155/pbxctrl tcp6 0 0 :::5061 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::2345 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::2346 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::80 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::22 :::* LISTEN 1808/sshd: /usr/sbi tcp6 0 0 ::1:25 :::* LISTEN 1122/exim4 tcp6 0 0 :::443 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::10050 :::* LISTEN 849/zabbix_agent2 tcp6 0 0 :::5060 :::* LISTEN 42155/pbxctrl it is running but cant access web gui. where can i see logs? and i just noticed "/etc/init.d/pbx status" doesnt work. it runs the command "checkproc pbx && echo OK || echo No process" debian or ubuntu doesnt have checkproc, maybe change this to pgrep or pidof

i tried that a while ago (early v68), and vodia has a hard time transcoding it, i would get silience on both ends.

must be a problem with zammad

i believe there is no setting for that, it will use the default windows device.

We are talking about the main admin password, not individual sip accounts. Yes I have seen that setting in the pbx.xml file. there should never be a instance where the main super admin has a blank password.

sent you a PM with the full screenshot.

lol. no wonder all my tickets that i created emailing: support@vodia.com or creating a ticket via support.vodia.com, nevers gets answered. no its for sure its there, hamlet confirmed when i called.

Ticket# 487882

Yes I attached it to my ticket about a week ago. pretty much the same as any grandstream phone. Same p values. It also support xml version 2, which grandstream introduced a while ago, which doesn’t require p values, instead it uses the names from the web gui. # SIP Server P47 = <!-- SIP Server --> <item name="account.1.sip.server.1.address"></item> I was thinking we can skip multicast and unicast if we can just assign the unit to an extension, and page the extension. By default it’s on auto answer. the problem with *cast, we must know the clients network. To make a speed dial button on the phone to be able to send a *cast to all intercom units. the other issues with just using *cast if client has multiple locations and they want to page another unit in another location.

I am glad I saw this, I was just told by support team that it is not possible to add our own templates. any chance to add Grandstream GSC3510 / GSC3505.

well that is expected, if you get access to any underlying server, all bets are off. once someone has access to the servers, they already have everything, all settings, trunks, web passwords. I think the point is that the PBX should look at that config and expect a password, not allow default to be blank. most software these days, auto generate a PW on install and then show it to the user, so they can login. or we need a command part of the install process, to create the main super user.

The PBX should not allow blank password. Reading https://doc.vodia.com/docs/login#admin-password-reset. This is incorrect way to handle password resets. If the PBX cant read that file, then PBX should assume there is a corrupts file, and not allow blank passwords. PBX should write to log file that it cant find the pbx.xml file, and not let any admin users login, until we insert a new MD5(password).