[Home]

Summary:ASTERISK-00384: IAX2- PUBLIC vs. NAT doenst like qualify = yes in iax.conf
Reporter:zoa (zoa)Labels:
Date Opened:2003-10-14 14:55:21Date Closed:2004-09-25 02:52:04
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:If i put a qualify=yes on the public box's iax.conf, IAX2 is no longer registering.

iax show peers correctly shows the status correctly (90ms)
iax2 show peers show --> status UNREACHABLE



****** ADDITIONAL INFORMATION ******

I am using latest cvs, natted box has x100p, public box has TE410p and has icmp blocked on the firewall.

Public box box:


[iax-test]
type=friend
allow=all
context=default
secret=secret
auth=plaintext
trunk=yes
;qualify=yes
host=dynamic


Natted box:

register => iax-test:secret@xxx.xxx.xxx.xxx

[iax-test]
type=friend
allow=all
context=default
secret=secret
auth=plaintext
trunk=yes
;qualify=yes
host=dynamic
Comments:By: Mark Spencer (markster) 2003-10-16 05:31:09

Does it matter if the registering host is behind NAT or not?
By: John Todd (jtodd) 2003-10-29 00:25:40.000-0600

zoa - can you see if you can update with an answer to Mark's question?
By: zoa (zoa) 2003-10-29 07:13:07.000-0600

oops, didnt see mark's question, i only have one public ip asterisk box, so i cannot really tell for sure.

Meanwhile i have another cvs version,  and i just tried to enable it again, and it worked.

(Although i also stopped using friend but use 2 entrys for user and peer now.)

cleopatra*CLI> show version
(Asterisk CVS-10/28/03-12:28:54 built by root@cleopatra on a i686 running Linux)

Case closed.
By: zoa (zoa) 2003-10-29 07:25:54.000-0600

hmmz, oké, i was too fast.

On the new cvs, the status for IAX2 and IAX works when qualify = yes on the private machine too.

But as soon as i tried to call in either direction, i get a timeout after a while, nothing happens.

When i tried to change it back to qualify= no (on the natted machine) and i did a reload, then i tried a reload on the public ip machine and it did not reload, i could not even stop it (started with safe_asterisk), nothing happened.

So the unreachable is gone, but it still doesnt look oké yet. (i think)

I'll do some more test tonight, the machine is in production atm, just got yelled at by the manager so will wait for more tests till everybody is gone.
By: zoa (zoa) 2003-10-29 07:26:44.000-0600

oh, i tried the reload on both machines two times, and two times the public ip server did not respond to command on the CLI, it did however print a new CLI> line after eacht return.
By: Brian West (bkw918) 2003-12-14 13:06:04.000-0600

Sounds like something else is blocking.. any update on this?
By: zoa (zoa) 2003-12-15 03:59:30.000-0600

i got rid of the natted situation, got me a new ip and it works now. :)
By: Brian West (bkw918) 2004-01-07 00:08:42.000-0600

I still need to know if this can be recreated... care to try zoa?
By: Brian West (bkw918) 2004-01-09 22:25:38.000-0600

This has been recently fixed..
By: Brian West (bkw918) 2004-01-09 22:25:48.000-0600

Fixed in CVS