MDTV
02-22-2008, 10:48 AM
I'm trying to neighbor my Tandberg GK to a Radvision ECS in India and vice versa. The India location is on our WAN. I can't seem to get it to work in either direction.
First, I have created a zone on the Tandberg with the IP of the India GK. The India GK has a zone prefix of "6" set, so I set the zone for a pattern match for "6". I have a hop count of 2.
When I dial from an endpoint registered to my Tandberg to an endpoint registered to the Radvision using the alias 6349 I get the following output on my Tandberg event log:
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Received" Service=H.225 Message Type=ARQ Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="SeqNo:4341 Call Type:PointToPoint Bandwidth:128 Kbits/sec" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=RIP Src-ip=172.26.221.80 Src-port=1719 Dst-ip=172.26.85.105 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:4341" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.notice gk: Event="Call Attempted" Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Protocol=UDP Level=1 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=LRQ Src-ip=172.26.221.80 Src-port=1719 Src-alias=E164:36344 Dst-ip=192.168.1.29 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="SeqNo:55915 HopCount:2 Bandwidth:128 Kbits/sec" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Received" Service=H.225 Message Type=LCF Src-ip=192.168.1.29 Src-port=1719 Dst-ip=172.26.221.80 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:55915" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.notice gk: Event="Call Rejected" Reason="ExceedsCallCapacity" Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="no route for bandwidth calculation" Protocol=UDP Level=1 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=ARJ Src-ip=172.26.221.80 Src-port=1719 Dst-ip=172.26.85.105 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:4341 Reason:ExceedsCallCapacity" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
It looks like the location request is getting sent to the India GK as it should, and it seems to send back a response. If I'm reading this correctly, the call seems to be failing on my end. Does anyone have any ideas on what I might be missing?
I'll post the opposite scenario later (neighboring India Radvision to my Tandberg.)
First, I have created a zone on the Tandberg with the IP of the India GK. The India GK has a zone prefix of "6" set, so I set the zone for a pattern match for "6". I have a hop count of 2.
When I dial from an endpoint registered to my Tandberg to an endpoint registered to the Radvision using the alias 6349 I get the following output on my Tandberg event log:
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Received" Service=H.225 Message Type=ARQ Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="SeqNo:4341 Call Type:PointToPoint Bandwidth:128 Kbits/sec" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=RIP Src-ip=172.26.221.80 Src-port=1719 Dst-ip=172.26.85.105 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:4341" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.notice gk: Event="Call Attempted" Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Protocol=UDP Level=1 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=LRQ Src-ip=172.26.221.80 Src-port=1719 Src-alias=E164:36344 Dst-ip=192.168.1.29 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="SeqNo:55915 HopCount:2 Bandwidth:128 Kbits/sec" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Received" Service=H.225 Message Type=LCF Src-ip=192.168.1.29 Src-port=1719 Dst-ip=172.26.221.80 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:55915" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.notice gk: Event="Call Rejected" Reason="ExceedsCallCapacity" Src-ip=172.26.85.105 Src-port=1719 Src-alias=E164:36344 Dst-ip=172.26.221.80 Dst-port=1719 Dst-alias=E164:6349 Call Serial Number=3844 Detail="no route for bandwidth calculation" Protocol=UDP Level=1 Time=2008-02/22 15:37:03
Feb 22 10:37:03 MGW-VC-GATEKEEP1 local0.info gk: Event="Message Sent" Service=H.225 Message Type=ARJ Src-ip=172.26.221.80 Src-port=1719 Dst-ip=172.26.85.105 Dst-port=1719 Call Serial Number=3844 Detail="SeqNo:4341 Reason:ExceedsCallCapacity" Protocol=UDP Level=2 Time=2008-02/22 15:37:03
It looks like the location request is getting sent to the India GK as it should, and it seems to send back a response. If I'm reading this correctly, the call seems to be failing on my end. Does anyone have any ideas on what I might be missing?
I'll post the opposite scenario later (neighboring India Radvision to my Tandberg.)