Re: LRQ for "gatekeeper-monitoring-check" from Tandberg VCS?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I think its ok if the other gatekeeper answers LRJ to the monitoring
check. It is just intended to see if the LRQs go through.

You could add a permanent endpoint with alias
"gatekeeper-monitoring-check" to make GnuGk respond with LCF, but I
don't think you need to.

Regards,
Jan


Robert Kulagowski wrote:
> I'm getting these every 30 seconds:
> 2009/08/25 15:21:51.817 4             RasSrv.cxx(230)   RAS 
> Receiving on 10.23.10.222:1719(U)
> 2009/08/25 15:21:51.817 2             RasSrv.cxx(189)   RAS     Read 
> from 10.244.22.20:1719
> 2009/08/25 15:21:51.817 3             RasSrv.cxx(238)   RAS
> locationRequest {
>      requestSeqNum = 41203
>      destinationInfo = 1 entries {
>        [0]=h323_ID  27 characters {
>          0067 0061 0074 0065 006b 0065 0065 0070   gatekeep
>          0065 0072 002d 006d 006f 006e 0069 0074   er-monit
>          006f 0072 0069 006e 0067 002d 0063 0068   oring-ch
>          0065 0063 006b                            eck
>        }
>      }
>      replyAddress = ipAddress {
>        ip =  4 octets {
>          0a f4 16 14                                        ....
>        }
>        port = 1719
>      }
>      sourceInfo = 1 entries {
>        [0]=h323_ID  27 characters {
>          0067 0061 0074 0065 006b 0065 0065 0070   gatekeep
>          0065 0072 002d 006d 006f 006e 0069 0074   er-monit
>          006f 0072 0069 006e 0067 002d 0063 0068   oring-ch
>          0065 0063 006b                            eck
>        }
>      }
>      canMapAlias = true
>      genericData = 1 entries {
>        [0]={
>          id = nonStandard  16 octets {
>            dd 4a ad ab 21 b6 11 dd  89 65 00 50 56 c0 00 08 
> .J..!....e.PV...
>          }
>          parameters = 1 entries {
>            [0]={
>              id = nonStandard  16 octets {
>                dd 4a ad ac 21 b6 11 dd  89 65 00 50 56 c0 00 08 
> .J..!....e.PV...
>              }
>              content = raw  16 octets {
>                dd 4a ad aa 21 b6 11 dd  89 65 00 50 56 c0 00 08 
> .J..!....e.PV...
>              }
>            }
>          }
>        }
>      }
>      hopCount = 1
>      callIdentifier = {
>        guid =  16 octets {
>          dd 4a ad aa 21 b6 11 dd  89 65 00 50 56 c0 00 08   .J..!....e.PV...
>        }
>      }
>      sourceEndpointInfo = 1 entries {
>        [0]=h323_ID  27 characters {
>          0067 0061 0074 0065 006b 0065 0065 0070   gatekeep
>          0065 0072 002d 006d 006f 006e 0069 0074   er-monit
>          006f 0072 0069 006e 0067 002d 0063 0068   oring-ch
>          0065 0063 006b                            eck
>        }
>      }
>    }
> 2009/08/25 15:21:51.818 5                job.cxx(190)   JOB     Starting 
> Job LRQ at Worker thread 3074124688
> 2009/08/25 15:21:51.818 5                job.cxx(364)   JOB     Worker 
> threads: 10 total - 10 busy, 0 idle
> 2009/08/25 15:21:51.818 1             RasSrv.cxx(368)   RAS     LRQ 
> Received from 10.244.22.20:1719
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy Explicit for the request LRQ 41203
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy Internal for the request LRQ 41203
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy Neighbor for the request LRQ 41203
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy ENUM for the request LRQ 41203
> 2009/08/25 15:21:51.818 4            Routing.cxx(1323)  ROUTING Policy 
> ENUM not supported for LRQ
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy SRV for the request LRQ 41203
> 2009/08/25 15:21:51.818 4           Neighbor.cxx(1531)  ROUTING Policy 
> SRV not supported for LRQ
> 2009/08/25 15:21:51.818 5              Routing.h(177)   ROUTING Checking 
> policy DNS for the request LRQ 41203
> 2009/08/25 15:21:51.818 4            Routing.cxx(611)   ROUTING Policy 
> DNS not supported for LRQ
> 2009/08/25 15:21:51.818 2             RasSrv.cxx(408) 
> LRJ|10.244.22.20|gatekeeper-monitoring-check:h323_ID
> 2009/08/25 15:21:51.818 3             RasSrv.cxx(250)   RAS     Send to 
> 10.244.22.20:1719
> locationReject {
>      requestSeqNum = 41203
>      rejectReason = requestDenied <<null>>
>    }
> 2009/08/25 15:21:51.818 5             RasSrv.cxx(264)   RAS     Sent 
> Successful
> 2009/08/25 15:21:51.818 5                job.cxx(427)   JOB     Job LRQ 
> deleted
> 
> 
> Is there something particular that it's looking for?  A statically 
> assigned EP or something like that so that the LRQ doesn't fail?


-- 
Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________________

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/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux