|
Hummm... I’ll
try to explain how thinks are tied together. Hoppefully it helps…. ;) SER recieves the INVITE
through IP X, port 5060/UDP (normal SIP port), identify that’s from a
NATed UA and prepare internal pointers. It also recognize the prefix (in this
case 9809) that flags the call to Yate. The call is relayed to Yate who is listenning
on IP X, but port 5080/UDP. Now Yate initiate the
negotiations as defined in its routing policy with its H323 side. Yate is
registering itself on GK1 as a Gateway (it’s not a permanent endpoint and
uses IP X, port 1730/UDP) but, as I didn’t find a way to register a
prefix from Yate itself I declare it in the [RasSrv::GWPrefixes] section. So
now the signalization part of the call is already on H323 side. Let’s start other
way around. T21 is registered as terminal on GK2 (normal port), which is
registered to GK1 (through normal port) with its own prefix (47 in this case). T01
is also registered on GK1 (through normal port – the port is changed on
the first packet by IPTables), but as a terminal. Since it’s on my
internal LAN, it’s registered as a NATed point. Now thinking back on the
call, it arrives on GK1, and using trace level 6, I see odd things: 1-
the packet arrives and generates a ACF (that’s ok); 2-
the packet is analised and forwarded to GK1 (that’s odd); 3-
this forwarded packet is followed by all FastStart required packets
(that’s ok); 4-
this forwarded packet recieves a ReleaseComplete, since the port
assigned is already on use by another Q.931 channel (the packet arrived and
trated on 1 & 2); 5-
call is Released with Q.931 error (not what I wanna, but what it
got); 6-
SIP side recieves a 404 (number/user not found). Forgive me if I didn’t
understand Your first question, but if You explain it a little bit more, maybe
I can provide You some valuable information. Edson From:
openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx
[mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of M.Emran Did u bridge yate
with GK2 ?you have to register yate to GK2 or you have to add yate ip to
permanent endpoint with prefix... On 7/5/07, Edson
<4lists@xxxxxxxxx> wrote:
You are right in pointing this port problem... At my first test Yate and GK1 were on the same
machine, but I let GK1 on port 1720 and changed Yate to port 1730.. didn't
work. Then I move Yate to SER machine… also didn't work. Know I have: - SER and Yate on same machine in a Internet
machine (SER on port 5060, MediaProxyand on ports 51000~51600 and Yate on port
5080 and RTP on ports 60000~65000); - GK1 on a machine in a Internet machine (all
default ports); - GK2 on my home border with ADSL connection. So I doubt that there is some port issue. I was
first thinking that it could be some routing issue, but since I can make a call
from T01, I give up from this thinking path. But again, thanks for Your thought…. Any
other? Edson From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx
[mailto: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of M.Emran yate and
gnugk are listening same port.try to change port from 1720 to 51720 of yate. hope it
will work. On
7/5/07, Edson < 4lists@xxxxxxxxx> wrote:
Hi...
|
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
