DUNDi Calls Only Work in One Direction


#1

Hello,

I posted this in the DUNDi section as well, but given the small number of topics I was hoping the additional traffic of this forum might yield a response/answer.

I am trying to get DUNDi working, but I can’t seem to get calls to work in both directions. I have two servers with the same install/updates, same module versions, and same config files (except for the dundi.conf where mac/ips/keys were changed accordingly) but for some reason calls in one direction will connect and in the other direction it will hang.

IAX are friends and DUNDi model is symmetric. I can query both directions show peers looks good and I couldn’t see anything with debug on.

I can post configs, but I was hoping this was a common problem with an easy fix.

HUNG CALL -
– Goto (macro-dundi-priv,5500,1)
– Called priv:pNsfOg6V3B2OIwFHrAiJMw==@192.16.1.53/5500

SUCCESSFUL CALL -
– Goto (macro-dundi-priv,5799,1)
– Called priv:RgQ5eVIqtBkQhBoIiHQtdQ==@192.168.1.38/5799
– Call accepted by 192.168.1.38 (format ulaw)
– Format for call is ulaw
– IAX2/192.168.1.38:4569-3538 is ringing
– Local/5799@trydundi-d3b7;1 is ringing
– IAX2/192.168.1.38:4569-3538 is ringing
– IAX2/192.168.1.38:4569-3538 stopped sounds
– IAX2/192.168.1.38:4569-3538 answered Local/5799@trydundi-d3b7;2
– Local/5799@trydundi-d3b7;1 stopped sounds
– Local/5799@trydundi-d3b7;1 answered SIP/5500-00000003

Any thoughts on what I might be missing are appreciated.


#2

My first thought is… Is there are firewall on 192.16.1.53 that may be dropping inbound port 4569?


#3

The servers are local to each other. No firewall between them.


#4

No offence intended, but if the servers are Linux, they have a firewall built it. Is it turned on? A simple check, as root, run the command: iptables -L

If it says:

[code]Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[/code]
Then the firewall is off. If it has more output, the firewall is on.
If running a Red Hat based distro such as CentOS, you could try the command:


#5

Turning that off was one of the first things I tried, but thanks for the advice. I would have loved for that to be the problem!


#6

Thanks for the help, but the problem turned out to be my mappings. I accidentally put 192.16.x.x (instead of 192.168.x.x) in one of the dundi.conf files. Argh!


#7

Glad to hear that you have it fixed. Yeah, bad IP does kinda look like a blocked port. It happens to me more often than I like to admit :blush: