Hi Ivan,
ACF|192.168.0.70:1720|9599_endp|30270|02116:dialedDigits|drj_gw2:h323_ID=00502d00260a:h323_ID|false;
The 02116 in the ACF is very strange. Something (presumably the VIP or the GK) is translating 01 to 02. From VIP command line do "atpm alist" and be sure that the Address entry for "0" has Prefix strip = 0 and Prefix Address = None. Make sure that this is the only entry starting with 0, and that the atpm config is active and saved.
Is there anything in your GK config that could be rewriting the number?
If you can't find anything obvious, run Ethereal and look at the number in the ARQ and in the ACF to see where it is getting altered.
I have some VIP-400 running with gnugk and can call from FXS ports ok.
--Stewart
----- Original Message ----- From: "Ivan Mitev" <imitev@xxxxxx>
To: <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, October 20, 2004 10:30 AM
Subject: calls from vip-000 fail
hello,
i run - successfully - gnugk with a testbed of soft clients, and with fxo gateways from micronet/gatewell.
i'm now testing a planet vip-000 gateway with both FXO and FXS modules, but i'm running into troubles:
- the gateway registers without any problem, with prefix 12
- i can make calls to the vip without problems from registered terminals / other gateways; (there is an atpm a-entry on the vip to direct 12xxx calls to the physical ports).
however i don't manage to make calls from the vip to other registered terminals/gateways. if i pick up a handset on the vip FXS side and i dial 01116, gnugk should route the call to the gateway registered with prefix 01, that will dial pbx extension 116. when using other terms/gws, that works like a charm.
on the vip, i think the atpm rules are ok ;
a-rule: tel 0 -> hunt 11 / min 5 / max 5 / 0 strip / 0 add
h-rule: hunt rule 11 has only d-rule 11 as member
d-rule: 11 -> H.323 Dest = 10.10.10.10/1720 TCP
10.10.10.10 is a bogus ip ; the vip will connect to the gk ip anyway when in gk mode.
that setup should be ok, since when i dial 01116 on the vip FXS side, i get an ACF on gnugk's status port:
ACF|192.168.0.70:1720|9599_endp|30270|02116:dialedDigits|drj_gw2:h323_ID=00502d00260a:h323_ID|false;
192.168.0.70 is the vip's ip, registered with id "drj_gw2"
however, nothing happens after this, until i get the following msg (timeout?), and the phone call ends:
DCF|192.168.0.70|9599_endp|30270|normalDrop;
if i do the same with the gateway "drj_gw1", with ip 192.168.0.69, everything works: (192.168.0.4 is the gateway registered with prefix 01)
ACF|192.168.0.69:1720|5023_endp|19794|01116:dialedDigits|drj_gw1:h323_ID=02:dialedDigits|false; ACF|192.168.0.4:1720|5024_endp|19753|01116:dialedDigits|drj_gw1:h323_ID=02:dialedDigits|true;
any clue ?
i've tested with gnugk 2.0.8, and 2.2beta4, on an old RH 7.3
what i think is the relevant config is :
gnugk (on host 192.168.0.3)
[RoutedMode] GKRouted=1 H245Routed=1 CallSignalPort=1720 RemoveH245AddressOnTunneling=1 AcceptUnregisteredCalls=1 AcceptNeighborsCalls=1 DropCallsByReleaseComplete=1 SendReleaseCompleteOnDRQ=1 SupportNATedEndpoints=1
[RasSrv::RRQFeatures] AcceptEndpointIdentifier=1
[RasSrv::ARQFeatures] CallUnregisteredEndpoints=1
and h323 params on the vip (over a clean conf):
set h323 gk_mode manual set h323 gk_id sp_gk1 set h323 gk_addr 192.168.0.3 set h323 endpoint_prefix 12
set h323 display_name drj_gw2 set h323 term_id drj_gw2
set h323 h245_tunneling on set h323 cisco_t38 off set h323 nat_call off set h323 allow_calls_wo_gk false
--------
thanks for your help !
ivan
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
