Problem update ivoz 4.6.0

[dbbrito]

Description

---

• IvozProvider version: 4.6.0

• Related sections:

  • SIP & Telephony
  • vPBX Functionalities
  • Billing & Invoicing
  • Web Interface
  • API
  • Other

Troubleshooting

We updated iVoz 4.4.0 on Debian 12 simply by logging in via SSH and typing apt-update and apt-upgrade -y, and it updated iVoz

to version 4.6.0. We had been using 4.4.0 for over a year now, as follows:

Proxies User:

proxyusers 10.0.0.100
users 10.0.0.50 Advertised IP 146.XXX.XXX.134

Proxies Trunk:
proxytrunks 10.0.0.51
trunks 10.0.0.101 Advertised IP 146.XXX.XXX.144

After the update, we also changed the interface in /etc/rtpengine/rtpengine.conf back to the configuration I had been using for a long time, and so far everything is fine; this 4.6.0 is making calls. It usually takes over 30 seconds, but we've encountered two problems: either something changed in version 4.6.0, because now when we call and the destination hangs up first, the softphone no longer hangs up, whereas in version 4.4.0 it would hang up on the softphone instantly if the recipient hung up first, another problem we've seen is that no international calls from our DIDs enter the ivozprovider, and through kamtail-proxytrunks we can see the message: [Feb 20 22:11:40] [6650bcdf] 146.XXX.XXX.144 is not one of my domains, 404 Not Here, note that 146.XXX.XXX.144 is the trunks IP address. Do you know of any change or alteration in any new configuration that could be causing this? Any help is welcome.

Thank you

[boxlostdvdr]

Same problem here, luckily I had taken a snapshot and restored everything.

[airsay]

So do any of you have your instances behind a NAT, say AWS? I have run into the same problem after updating from v4.5. Temporary fix that seems to be working is to put an alias=PUBLIC_IP immediately after the line that includes listeners.cfg in /etc/kamailio/proxytrunks/kamailio.cfg

[airsay]

So I have "patched" this by editing /etc/kamailio/proxytrunks/listeners.cfg and /etc/kamailio/proxyusers/listeners.cfg.

It seems as though, the "advertised IP address" from the GUI isn't getting written to these files. Editing them normally (sudo nano or sudo vi) gets overwritten when Kamailio is restarted. So I've kept the edits by making the files "immutable" after edits. So:

sudo nano /etc/kamailio/proxytrunks/listeners.cfg

then sudo chattr -i /etc/kamailio/proxytrunks/listeners.cfg

Same for proxyusers. Calls from the trunks no longer get a 404. Still testing but I'm hoping this holds up until Irontec can get to the bottom of it.

I suspect that the new changes to add additional_address.cfg for both instances of Kamailio hasn't been properly implemented.

@dbbrito can you test on your end? Also you mentioned changing IP address for interface in rtpengine.conf. Are switching from users IP to trunk? That's the only way I can get two-way audio. I changed it to trunk_internal_IP!trunk_external_IP and I have audio both ways. Also ran into issues with asterisk sending a 603 for all internal extension calls. Fixed that by restarting fastagi.socket:

sudo systemctl restart fastagi.socket

Tons of troubleshooting today

[danigargar]

Hi!

The issue seems to be that Kamailio doesn't reload after updating the proxy trunk; if I change the advertised IP and reload Kamailio manually, I can see listeners.cfg updated correctly. Can you confirm if this is the issue?

Best regrads

[airsay]

Hi @danigargar

On the GUI(Platform>Infrastructure) I have changed the advertised address for both trunk and users, restarted Kamailio using:

sudo restart kamailio@users.service kamailio@trunks.service

And viewed listeners using

sudo nano /etc/kamailio/proxytrunks/listeners.cfg
sudo nano /etc/kamailio/proxytrunks/listeners.cfg

And neither of the listeners.cfg displays any advertised address.

How are you getting yours done?

Regards
airsay

Hi!

The issue seems to be that Kamailio doesn't reload after updating the proxy trunk; if I change the advertised IP and reload Kamailio manually, I can see listeners.cfg updated correctly. Can you confirm if this is the issue?

Best regrads

[airsay]

@danigargar do you want to clarify what you meant by: “if I change the advertised IP and reload Kamailio manually”?

I already have the advertised IP set via the GUI but no matter how many times I restart Kamailio, the issue still persists. On both proxyUsers and proxyTrunks, the internal IP is what appears on the Record-Route header resulting in calls getting hung up after 32 seconds because the ACK response to the 200 OK cannot be routed. Please advise