Thanks tlpeter, Site A has been configured with two networks: LAN1 and LAN2.
The route to Site B is through the interface on LAN2.
So I've got a route on the IPO in Site A from LAN1 to LAN2 (on site A) and a route from LAN2 on Site A to Site B. Site B is configured with one network.
Tipter, I changed the ascii in the trace to protect the innocent. The true actual user in the error msg does exist.
The trace is what you see on site B when the call is placed from the "dual homed" site A.
Able to use system status at either site to ping any interface, from LAN1 or LAN2 in site...
Thanks for your suggestions.
Here is a failed call from A to B. Sysmon is running on site B. The source address: 192.168.16.2 is the LAN2 interface at Site A. The call was initiated from LAN 1 at Site A
UNICODE-UTF8
enu
240301185mS H323Rx: 16 src=192.168.16.2:4275
H323...
Thanks amriddle, Will do.
BAS1234 the sysmon trace files from the remote site indicate that reply to the h323 call setup request, is addressed to the gatekeeper on LAN2, instead of the gatekeeper on LAN1, where the call originated. Why I was wondering if I should disable it.
A followup question re: LAN1 and LAN2 on IPO 406V2
Should the H323 gatekeeper be disabled on LAN2 if that interface is being only being used to route to a gatekeeper in another office. Call processing is already being initiated by H323 gatekeeper on LAN1. I'm having a problem getting calls...
That is correct> But lets reverse it: Site A has two interfaces LAN1 and LAN2, with the IPO gatekeeper on LAN 1.
I can ping Site B from Site A but can't call. From Site B I can call or ping Site A. IPOs at both sites are connected directly to MPLS router.
LAN 2 on the IP office is connected directly to the MPLS provider router. I've disabled/enabled fw on LAN2 but has not change outcome. At the moment have TCP UDP and ICMP enabled in and out.
I've got port 8 enabled as LAN 2 on an IP 406 V2. Connected to an MPLS, I'm trying to place calls on a voip trunk to a second branch. I am able to ping from the private lan (LAN 1) to the branch, and from the branch to the private lan.
With H323 tracing enabled, when I try to place a call...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.