[Asterisk-Users] Infite RTP to wrong address from DG104S

[Zot O'Connor]

[I have found further info in ethereal down at the bottom of the note]

I have a dual homed asterisk box like this:

I have real and fake number on the same LAN, and the fireall is aware of
this:

FW/GW  real IP eth0 (Filtered)
       fake IP eth0:1 (NATTED)

        ---------------------real IP eth0
Asterisk
Box     ---------------------Fake IP eth0:1
                |
                |
              DG104S

The DG is unaware of the Real numbers, but has uses the gateway.

I had it on the old box (FC1) in the same way, different base IP number.

It worked.

I pulled the XP100 and installed asterisk on the new box (RH9) (I will
use nuphone for a few hours outbound).

I rsynced the /etc files over, and the src.

I ran "make clean install" on the new box (RH9)

Now when I dial out the DG104S, it works the first time, slightly better
since I get a dialtone instead of a fast busy, but after a while it does
not respond.

Checking tethereal I see a 

1831.249249 DG_FAKE_IP -> ASTERISK_REAL_IP RTP Payload type=ITU-T G.711 PCMU, SSRC=24251, Seq=12158, Time=1952639
1831.249594 DG_FAKE_IP -> ASTERISK_REAL_IP RTP Payload type=ITU-T G.711 PCMU, SSRC=24251, Seq=12158, Time=1952639

I have to reset the DG104S to make it stop.  Other ports work at least
initially while this is going on.  reload, or stopping and starting
asterisk does not seem to do anything.

Now in order for the DG to now about the fake Asterisk IP, asterisk has
to tell it.

In /etc/mgcp.conf I have:
bindaddr = FAKE_ASTERISK_IP


So what causes the DG to see the ASTERISK_REAL_IP and how can I stop it?

Other than the zap channel being missing for the moment, anf the base IP
number being different everything is identical.

Any ideas?  Thanks!


I did update the DH104S with the new asterisk IP (the old one is offline
at the moment).

------------------------- 

I caught the problem in ethereal:

In looking at the packets leading to the RTP packs I see an MGCP packet
from FAKE_ASTERISK_IP to FAKE_DG_IP that contains the REAL_ASTERISK_IP
in the connection information fields, and in the owner/creator fields


So how do I tell asterisk to stop leaking information about eth0?

I am now watching a call that works.

Any more ideas :) Thanks!

-- 
Zot O'Connor <zot at zotconsulting.com>
White Knight Hackers, Inc.