SCN Issue

[MikeSide]

Hi everyone,

I have a big weird problem with 2 new system on scn. I explain,

S1 : 8.1(63) + VM PRO
S2 : 8.1(65) + VM PRO

I have put the small community between the two system. Everything work fine at first shot. The second day, we make a change and need to reboot the S2. After the reboot, it impossible to make a call interSite. The link are UP each site. That ping each site. the network are a point to point with all port open.

So what i've do for that :
1 - Reboot all system
2 - Reboot the 2 routeurs
3 - Delete H323 Line and recreate
4 - Centralize the VM at S2 and S1 as the main VM

Nothing work so i put my SCN config at H450 and create shortcode 2XX/Dial/2N/18... That Work....

I have pass more then 14 hours and put 3 tech on the problem, nobody find it...

so if somebody have the miracle solution... please tell me your secret !!!

Thank

 

[MikeSide]

Yes probably that the easy way but i can't do that, one are in quebec and the other at Montreal 100% operational so... i need to fix it without that solution.

 

[hairlessupportmonkey]

I doubt its the WG unless you are using an H323 Proxy Policy. If you are, dont.

The Juniper must also have any H323 type ALG disabled.

You could be evil and create a site to site VPN along the fibre to rule out NAT / FW / Routing issues


ACSS - SME
General Geek

 

[MikeSide]

Look the report up, the wachgard pass

FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=50795/udp, src_ip=10.0.0.253, src_port=50795, dst_ip=192.168.2.254, dst_port=50795, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=43, ttl=98
2013-06-13 17:46:23
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=50795/udp, src_ip=10.0.0.253, src_port=50795, dst_ip=192.168.2.254, dst_port=50795, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=43, ttl=98
2013-06-13 17:46:33
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=50795/udp, src_ip=10.0.0.253, src_port=50795, dst_ip=192.168.2.254, dst_port=50795, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=43, ttl=98
2013-06-14 05:46:59
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=50795/udp, src_ip=192.168.2.254, src_port=50795, dst_ip=10.0.0.253, dst_port=50795, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=43, ttl=95
2013-06-14 05:47:08
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=50795/udp, src_ip=192.168.2.254, src_port=50795, dst_ip=10.0.0.253, dst_port=50795, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=43, ttl=95
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4151, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 5780 win 32
2013-06-13 11:31:02
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4152, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 1488 win 32
2013-06-13 11:31:14
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=1720/tcp, src_ip=10.0.0.253, src_port=4161, dst_ip=192.168.2.254, dst_port=1720, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=44, ttl=98, pr_info=offset 6 S 20515 win 32
2013-06-13 11:31:47
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4153, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 55423 win 32
2013-06-13 11:32:29
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=1720/tcp, src_ip=10.0.0.253, src_port=4162, dst_ip=192.168.2.254, dst_port=1720, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=44, ttl=98, pr_info=offset 6 S 20040 win 32
2013-06-13 11:32:31
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4154, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 43567 win 32
2013-06-13 11:33:17
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4155, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 31967 win 32
2013-06-13 11:33:44
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE2-00, protocol=1720/tcp, src_ip=10.0.0.253, src_port=4163, dst_ip=192.168.2.254, dst_port=1720, src_intf=1-Trusted, dst_intf=3-Optional-2, rc=100, pckt_len=44, ttl=98, pr_info=offset 6 S 20077 win 32
2013-06-13 11:34:02
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4156, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 20111 win 32
2013-06-13 11:34:47
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=1720/tcp, src_ip=192.168.2.254, src_port=4157, dst_ip=10.0.0.253, dst_port=1720, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=44, ttl=95, pr_info=offset 6 S 7999 win 32
2013-06-13 11:34:49
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=icmp, src_ip=192.168.2.254, dst_ip=10.0.0.253, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=60, ttl=95
2013-06-13 11:34:50
FWAllow, Allowed, pri=4, disp=Allow, policy=FIBRE-00, protocol=icmp, src_ip=192.168.2.254, dst_ip=10.0.0.253, src_intf=3-Optional-2, dst_intf=1-Trusted, rc=100, pckt_len=60, ttl=95

but on the juniper

we have found something else

H323 Menu -- Check enable

Application screen :
Nat mode (unchek)
Route mode (uncheck)
Get source port any (uncheck)
Message flood (uncheck)
H323 and sip check on application layer gateway

 

[MikeSide]

Nobody know about the h323 router configuration ?

 

[amriddle01]

Being Avaya IP Office engineers as oppose to Watchguard/Juniper trained network engineers....possibly not



"No problem monkey socks

 

[MikeSide]

yeah sure..

Im gonna upgrade the 2 system at 8.1(69) just to be sure that not a dtmf problem on SCN also, im gonna put a level 3 network technician on the case...

 

[hairlessupportmonkey]

Actually - I am also a watchguard engineer too (Not Juniper)



ACSS - SME
General Geek