Re: [OSL | CCIE_Voice] Basic H323 trunking with CUBE and GK - ring no connect

2012-11-14 Thread Sergey Heyphets
Thanks Kevin.

First thing I tried, was unchecking Wait for far side TCS on the trunk
and resetting the trunk. After that, the caller gets fast busy immediately
after 3001 picks up.

I'll check the h245 traces on the CUCM to see what's going there. But the
call completes successfully without CUBE, so if there is a h245 issue, it
must be CUBE related. Would CUBE try to do slow-start to fast-start
conversion by default, requiring transcoding resources?

Sergey



On Wed, Nov 14, 2012 at 1:48 AM, Kevin Spicer ke...@kevinspicer.co.ukwrote:

 It's deadlocked, both cucm and cube are waiting for the other to send
 TCS.  On the trunk, uncheck Wait for far side TCS.  Alternatively add an
 MTP and configure the trunk for fast start.
 On 14 Nov 2012 04:06, Sergey Heyphets ser...@heyphets.com wrote:

 Hi All,

 I'm trying to basic H323 GK-controlled trunk with CUBE between CUCM and
 UCM Express. The topology looks like this:

 5001-CUCM ---GK/CUBE (HQ router)  GW (BR2 router)-3001

 CUCM, CUBE and GW all register to GK. The configuration is very basic
 with zone prefixes and outvia zone shown below. The behavior I see:
 1) CUCM phone (5001) calls 3001
 2) CUCM exchanges ARQ/ACF, sends SETUP to CUBE
 3) CUBE exchanges ARQ/ACF, sends SETUP to BR2
 4) BR2 exchanges ARQ/ACF, sends ALERTING, 3001 rings, 5001 gets ring tone.
 At this point, the show gatekeeper calls looks like this:

 Total number of active calls = 2.
  GATEKEEPER CALL INFO
  
 LocalCallIDAge(secs)   BW
 5-3300513  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: gk-trunk_15001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.10.30   53963 192.168.10.30   51666
  Endpt(s): Alias E.164Addr
dst EP: HQ3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
 LocalCallIDAge(secs)   BW
 6-3300512  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: HQ5001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
  Endpt(s): Alias E.164Addr
dst EP: BR2   3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.41720  192.168.50.463228


 5) 3001 picks up, BR2 sends CONNECT, CUBE sends PROGRESS
 6) 5001 still gets ringback tone for several seconds, then gets fast
 busy.

 See the output of the debug h225 q931  from HQ below. I did bunch of
 different backups, but I still can't figure out why CUBE wouldn't forward
 the CONNECT. The codec is g711ulaw on both sides.

 If I remove CUBE (e.g. remove outvia zone), everything connects
 perfectly.  What am I missing?


 HQ Config:
 voice service voip
  allow-connections h323 to h323
  allow-connections h323 to sip
  allow-connections sip to h323
  fax protocol cisco
 !
 !
 !
 voice class codec 1
  codec preference 1 g711ulaw
  codec preference 2 g729r8
 !
 interface Loopback0
  ip address 192.168.50.2 255.255.255.255
  h323-gateway voip interface
  h323-gateway voip id CUBE ipaddr 192.168.50.2 1719
  h323-gateway voip h323-id HQ
  h323-gateway voip bind srcaddr 192.168.50.2

 dial-peer voice 300 voip
  incoming called-number 3...
  codec g711ulaw
 !
 dial-peer voice 301 voip
  destination-pattern 3...
  session target ras
  codec g711ulaw

 gateway
  timer receive-rtp 1200
 !
 !
 !
 gatekeeper
  zone local CUBE cisco.com 192.168.50.2
  zone local UCME cisco.com outvia CUBE
  zone local UCM cisco.com
  zone prefix UCM 1... gw-priority 10 gk-trunk_2
  zone prefix UCME 3...
  zone prefix UCM 5... gw-priority 10 gk-trunk_2
  gw-type-prefix 1#* default-technology
  no shutdown
 
 HQ#show gatek end
 GATEKEEPER ENDPOINT REGISTRATION
 
 CallSignalAddr  Port  RASSignalAddr   Port  Zone Name Type
  Flags
 --- - --- - - 
  -
 192.168.10.30   53963 192.168.10.30   51666 UCM   VOIP-GW
 H323-ID: gk-trunk_1
 Voice Capacity Max.=  Avail.=  Current.= 0
 192.168.50.21720  192.168.50.253199 CUBE  H323-GW
 H323-ID: HQ
 Voice Capacity Max.=  Avail.=  Current.= 0
 192.168.50.41720  192.168.50.463228 UCME  VOIP-GW
 H323-ID: BR2
 E164-ID: 3001
 E164-ID: 3002
 Voice Capacity Max.=  Avail.=  Current.= 0
  Total number of active registrations = 3

 -
 debug h225 q931 from CUBE:
 HQ#debug h225 q931
 H.225 Q931 IE Details debugging is on
 HQ#
   Q931 Message IE Decodes
 Protocol Discriminator : 0x08
 CRV 

Re: [OSL | CCIE_Voice] Basic H323 trunking with CUBE and GK - ring no connect

2012-11-14 Thread Bill Lake
I believe that Cube never initiates tcs on its call leg with ccm by design
(as its the middle man) and only responds to tcs. If ccm waits for far end
tcs, then media connect will timeout. So if you have it checked in CUCM and
no one ever responds, it just waits.  This is shown in the trace on CUCM
and is worth trying.

On Wed, Nov 14, 2012 at 3:12 PM, Sergey Heyphets ser...@heyphets.comwrote:

 I'm no expert on CUBE, but since CUBE proxies the RTP and provides the
 transcoding capabilities, it must participate in the H.245 exchange.
 Otherwise, it wouldn't be able to send it's own IP addresses in the OLC
 messages and different codecs in the TCS to different parties.  In fact I
 saw TCS exchange in the debug h245 asn1 on CUBE, but only when no other
 debug was enabled.



 On Wed, Nov 14, 2012 at 1:28 PM, Bill Lake whl...@gmail.com wrote:

 won't show anything, CUBE does not do this part, that is why you have a
 stand off, must be done in CUCM



 On Wed, Nov 14, 2012 at 8:10 AM, Sergey Heyphets ser...@heyphets.comwrote:

 Thanks Bill.

 I tried looking at the h245 traces on the router, but for some reason
 debug h245 asn1 doesn't actually show anything when debug h225 q931 is
 active. I'll look at the CUCM side.


 On Wed, Nov 14, 2012 at 8:54 AM, Bill Lake whl...@gmail.com wrote:

 Hello,

 You need to look at the h245 information, you can do by set up traces
 in CUCM servicability, look at the H245 items, make the call.  You can
 then tail it from a ssh session or use RTMT to view the last 5 minutes or
 so and find your H245 issue.

 Bill

 On Tue, Nov 13, 2012 at 10:06 PM, Sergey Heyphets 
 ser...@heyphets.comwrote:

 Hi All,

 I'm trying to basic H323 GK-controlled trunk with CUBE between CUCM
 and UCM Express. The topology looks like this:

 5001-CUCM ---GK/CUBE (HQ router)  GW (BR2
 router)-3001

 CUCM, CUBE and GW all register to GK. The configuration is very basic
 with zone prefixes and outvia zone shown below. The behavior I see:
 1) CUCM phone (5001) calls 3001
 2) CUCM exchanges ARQ/ACF, sends SETUP to CUBE
 3) CUBE exchanges ARQ/ACF, sends SETUP to BR2
 4) BR2 exchanges ARQ/ACF, sends ALERTING, 3001 rings, 5001 gets ring
 tone.
 At this point, the show gatekeeper calls looks like this:

 Total number of active calls = 2.
  GATEKEEPER CALL INFO
  
 LocalCallIDAge(secs)   BW
 5-3300513  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: gk-trunk_15001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.10.30   53963 192.168.10.30   51666
  Endpt(s): Alias E.164Addr
dst EP: HQ3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
 LocalCallIDAge(secs)   BW
 6-3300512  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: HQ5001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
  Endpt(s): Alias E.164Addr
dst EP: BR2   3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.41720  192.168.50.463228


 5) 3001 picks up, BR2 sends CONNECT, CUBE sends PROGRESS
 6) 5001 still gets ringback tone for several seconds, then gets fast
 busy.

 See the output of the debug h225 q931  from HQ below. I did bunch of
 different backups, but I still can't figure out why CUBE wouldn't forward
 the CONNECT. The codec is g711ulaw on both sides.

 If I remove CUBE (e.g. remove outvia zone), everything connects
 perfectly.  What am I missing?


 HQ Config:
 voice service voip
  allow-connections h323 to h323
  allow-connections h323 to sip
  allow-connections sip to h323
  fax protocol cisco
 !
 !
 !
 voice class codec 1
  codec preference 1 g711ulaw
  codec preference 2 g729r8
 !
 interface Loopback0
  ip address 192.168.50.2 255.255.255.255
  h323-gateway voip interface
  h323-gateway voip id CUBE ipaddr 192.168.50.2 1719
  h323-gateway voip h323-id HQ
  h323-gateway voip bind srcaddr 192.168.50.2

 dial-peer voice 300 voip
  incoming called-number 3...
  codec g711ulaw
 !
 dial-peer voice 301 voip
  destination-pattern 3...
  session target ras
  codec g711ulaw

 gateway
  timer receive-rtp 1200
 !
 !
 !
 gatekeeper
  zone local CUBE cisco.com 192.168.50.2
  zone local UCME cisco.com outvia CUBE
  zone local UCM cisco.com
  zone prefix UCM 1... gw-priority 10 gk-trunk_2
  zone prefix UCME 3...
  zone prefix UCM 5... gw-priority 10 gk-trunk_2
  gw-type-prefix 1#* default-technology
  no shutdown
 
 HQ#show gatek end
 GATEKEEPER ENDPOINT REGISTRATION
 
 CallSignalAddr  Port  RASSignalAddr   

Re: [OSL | CCIE_Voice] Basic H323 trunking with CUBE and GK - ring no connect

2012-11-14 Thread Sergey Heyphets
Hi All,

Reporting back.

I had 2 issues in the configuration. As Bill and Kevin indicated, both CUBE
and CUCM were waiting to receive TCS from remote side first (not
configurable in CUBE, Wait for Far End H.245 Terminal Capability Set
checkbox in the H323 trunk configuration in CUCM). When I originally
unchecked the the Wait for TCS checkbox in CUCM, the called failed right
after it was answered by 3001.  That happened, because of the second issue
- the incoming dial peer on CUBE/HQ didn't have codec g711ulaw configured
(defaulting to g729), while outgoing dial peer had g711ulaw, so when call
would connect, there was a codec mismatch and CUBE would release the call.

Now that I have fixed the codec on the dial peer and removed the Wait for
TCS checkbox, the call connects successfully.

Thanks for your help guys!







On Wed, Nov 14, 2012 at 6:17 PM, Bill Lake whl...@gmail.com wrote:

 I believe that Cube never initiates tcs on its call leg with ccm by
 design (as its the middle man) and only responds to tcs. If ccm waits for
 far end tcs, then media connect will timeout. So if you have it checked
 in CUCM and no one ever responds, it just waits.  This is shown in the
 trace on CUCM and is worth trying.


 On Wed, Nov 14, 2012 at 3:12 PM, Sergey Heyphets ser...@heyphets.comwrote:

 I'm no expert on CUBE, but since CUBE proxies the RTP and provides the
 transcoding capabilities, it must participate in the H.245 exchange.
 Otherwise, it wouldn't be able to send it's own IP addresses in the OLC
 messages and different codecs in the TCS to different parties.  In fact I
 saw TCS exchange in the debug h245 asn1 on CUBE, but only when no other
 debug was enabled.



 On Wed, Nov 14, 2012 at 1:28 PM, Bill Lake whl...@gmail.com wrote:

 won't show anything, CUBE does not do this part, that is why you have a
 stand off, must be done in CUCM



 On Wed, Nov 14, 2012 at 8:10 AM, Sergey Heyphets ser...@heyphets.comwrote:

 Thanks Bill.

 I tried looking at the h245 traces on the router, but for some reason
 debug h245 asn1 doesn't actually show anything when debug h225 q931 is
 active. I'll look at the CUCM side.


 On Wed, Nov 14, 2012 at 8:54 AM, Bill Lake whl...@gmail.com wrote:

 Hello,

 You need to look at the h245 information, you can do by set up traces
 in CUCM servicability, look at the H245 items, make the call.  You
 can then tail it from a ssh session or use RTMT to view the last 5
 minutes or so and find your H245 issue.

 Bill

 On Tue, Nov 13, 2012 at 10:06 PM, Sergey Heyphets ser...@heyphets.com
  wrote:

 Hi All,

 I'm trying to basic H323 GK-controlled trunk with CUBE between CUCM
 and UCM Express. The topology looks like this:

 5001-CUCM ---GK/CUBE (HQ router)  GW (BR2
 router)-3001

 CUCM, CUBE and GW all register to GK. The configuration is very basic
 with zone prefixes and outvia zone shown below. The behavior I see:
 1) CUCM phone (5001) calls 3001
 2) CUCM exchanges ARQ/ACF, sends SETUP to CUBE
 3) CUBE exchanges ARQ/ACF, sends SETUP to BR2
 4) BR2 exchanges ARQ/ACF, sends ALERTING, 3001 rings, 5001 gets ring
 tone.
 At this point, the show gatekeeper calls looks like this:

 Total number of active calls = 2.
  GATEKEEPER CALL INFO
  
 LocalCallIDAge(secs)   BW
 5-3300513  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: gk-trunk_15001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.10.30   53963 192.168.10.30   51666
  Endpt(s): Alias E.164Addr
dst EP: HQ3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
 LocalCallIDAge(secs)   BW
 6-3300512  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: HQ5001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
  Endpt(s): Alias E.164Addr
dst EP: BR2   3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.41720  192.168.50.463228


 5) 3001 picks up, BR2 sends CONNECT, CUBE sends PROGRESS
 6) 5001 still gets ringback tone for several seconds, then gets fast
 busy.

 See the output of the debug h225 q931  from HQ below. I did bunch of
 different backups, but I still can't figure out why CUBE wouldn't forward
 the CONNECT. The codec is g711ulaw on both sides.

 If I remove CUBE (e.g. remove outvia zone), everything connects
 perfectly.  What am I missing?


 HQ Config:
 voice service voip
  allow-connections h323 to h323
  allow-connections h323 to sip
  allow-connections sip to h323
  fax protocol cisco
 !
 !
 !
 voice class codec 1
  codec preference 1 g711ulaw
  codec preference 2 g729r8
 !
 interface Loopback0
  ip 

[OSL | CCIE_Voice] Basic H323 trunking with CUBE and GK - ring no connect

2012-11-13 Thread Sergey Heyphets
Hi All,

I'm trying to basic H323 GK-controlled trunk with CUBE between CUCM and UCM
Express. The topology looks like this:

5001-CUCM ---GK/CUBE (HQ router)  GW (BR2 router)-3001

CUCM, CUBE and GW all register to GK. The configuration is very basic with
zone prefixes and outvia zone shown below. The behavior I see:
1) CUCM phone (5001) calls 3001
2) CUCM exchanges ARQ/ACF, sends SETUP to CUBE
3) CUBE exchanges ARQ/ACF, sends SETUP to BR2
4) BR2 exchanges ARQ/ACF, sends ALERTING, 3001 rings, 5001 gets ring tone.
At this point, the show gatekeeper calls looks like this:

Total number of active calls = 2.
 GATEKEEPER CALL INFO
 
LocalCallIDAge(secs)   BW
5-3300513  128(Kbps)
 Endpt(s): Alias E.164Addr
   src EP: gk-trunk_15001
   CallSignalAddr  Port  RASSignalAddr   Port
   192.168.10.30   53963 192.168.10.30   51666
 Endpt(s): Alias E.164Addr
   dst EP: HQ3001
   CallSignalAddr  Port  RASSignalAddr   Port
   192.168.50.21720  192.168.50.253199
LocalCallIDAge(secs)   BW
6-3300512  128(Kbps)
 Endpt(s): Alias E.164Addr
   src EP: HQ5001
   CallSignalAddr  Port  RASSignalAddr   Port
   192.168.50.21720  192.168.50.253199
 Endpt(s): Alias E.164Addr
   dst EP: BR2   3001
   CallSignalAddr  Port  RASSignalAddr   Port
   192.168.50.41720  192.168.50.463228


5) 3001 picks up, BR2 sends CONNECT, CUBE sends PROGRESS
6) 5001 still gets ringback tone for several seconds, then gets fast busy.

See the output of the debug h225 q931  from HQ below. I did bunch of
different backups, but I still can't figure out why CUBE wouldn't forward
the CONNECT. The codec is g711ulaw on both sides.

If I remove CUBE (e.g. remove outvia zone), everything connects perfectly.
 What am I missing?


HQ Config:
voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 fax protocol cisco
!
!
!
voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g729r8
!
interface Loopback0
 ip address 192.168.50.2 255.255.255.255
 h323-gateway voip interface
 h323-gateway voip id CUBE ipaddr 192.168.50.2 1719
 h323-gateway voip h323-id HQ
 h323-gateway voip bind srcaddr 192.168.50.2

dial-peer voice 300 voip
 incoming called-number 3...
 codec g711ulaw
!
dial-peer voice 301 voip
 destination-pattern 3...
 session target ras
 codec g711ulaw

gateway
 timer receive-rtp 1200
!
!
!
gatekeeper
 zone local CUBE cisco.com 192.168.50.2
 zone local UCME cisco.com outvia CUBE
 zone local UCM cisco.com
 zone prefix UCM 1... gw-priority 10 gk-trunk_2
 zone prefix UCME 3...
 zone prefix UCM 5... gw-priority 10 gk-trunk_2
 gw-type-prefix 1#* default-technology
 no shutdown

HQ#show gatek end
GATEKEEPER ENDPOINT REGISTRATION

CallSignalAddr  Port  RASSignalAddr   Port  Zone Name TypeFlags
--- - --- - - -
192.168.10.30   53963 192.168.10.30   51666 UCM   VOIP-GW
H323-ID: gk-trunk_1
Voice Capacity Max.=  Avail.=  Current.= 0
192.168.50.21720  192.168.50.253199 CUBE  H323-GW
H323-ID: HQ
Voice Capacity Max.=  Avail.=  Current.= 0
192.168.50.41720  192.168.50.463228 UCME  VOIP-GW
H323-ID: BR2
E164-ID: 3001
E164-ID: 3002
Voice Capacity Max.=  Avail.=  Current.= 0
Total number of active registrations = 3
-
debug h225 q931 from CUBE:
HQ#debug h225 q931
H.225 Q931 IE Details debugging is on
HQ#
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length : 2
CRV Value  : 0x0003
Message Type   : 0x05: SETUP
 Bearer Capability: Length Of IE=3
 Data 8090A2
 Calling Party Number: Length Of IE=6
 Data 008135303031
 Called Party Number: Length Of IE=5
 Data 8033303031
 User-User: Length Of IE=193
 Data
0520B0060008914A00050201808334401F003500300030003122C0B5120F436973636F43616C6C4D616E61676572003100010180633400801B43EDDC15310A03000301C0A8D26E00D50D8700C0A80A1ED2CB1100801B43EDDC15310A03000301C0A8D26E010001000100010010A00100140140B5120D82040020040001030003000103
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length : 2
CRV Value  : 0x8003
Message Type   : 0x02: CALL_PROC
 User-User: Length Of IE=70
 Data

Re: [OSL | CCIE_Voice] Basic H323 trunking with CUBE and GK - ring no connect

2012-11-13 Thread Kevin Spicer
It's deadlocked, both cucm and cube are waiting for the other to send TCS.
On the trunk, uncheck Wait for far side TCS.  Alternatively add an MTP and
configure the trunk for fast start.
On 14 Nov 2012 04:06, Sergey Heyphets ser...@heyphets.com wrote:

 Hi All,

 I'm trying to basic H323 GK-controlled trunk with CUBE between CUCM and
 UCM Express. The topology looks like this:

 5001-CUCM ---GK/CUBE (HQ router)  GW (BR2 router)-3001

 CUCM, CUBE and GW all register to GK. The configuration is very basic with
 zone prefixes and outvia zone shown below. The behavior I see:
 1) CUCM phone (5001) calls 3001
 2) CUCM exchanges ARQ/ACF, sends SETUP to CUBE
 3) CUBE exchanges ARQ/ACF, sends SETUP to BR2
 4) BR2 exchanges ARQ/ACF, sends ALERTING, 3001 rings, 5001 gets ring tone.
 At this point, the show gatekeeper calls looks like this:

 Total number of active calls = 2.
  GATEKEEPER CALL INFO
  
 LocalCallIDAge(secs)   BW
 5-3300513  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: gk-trunk_15001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.10.30   53963 192.168.10.30   51666
  Endpt(s): Alias E.164Addr
dst EP: HQ3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
 LocalCallIDAge(secs)   BW
 6-3300512  128(Kbps)
  Endpt(s): Alias E.164Addr
src EP: HQ5001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.21720  192.168.50.253199
  Endpt(s): Alias E.164Addr
dst EP: BR2   3001
CallSignalAddr  Port  RASSignalAddr   Port
192.168.50.41720  192.168.50.463228


 5) 3001 picks up, BR2 sends CONNECT, CUBE sends PROGRESS
 6) 5001 still gets ringback tone for several seconds, then gets fast busy.

 See the output of the debug h225 q931  from HQ below. I did bunch of
 different backups, but I still can't figure out why CUBE wouldn't forward
 the CONNECT. The codec is g711ulaw on both sides.

 If I remove CUBE (e.g. remove outvia zone), everything connects perfectly.
  What am I missing?


 HQ Config:
 voice service voip
  allow-connections h323 to h323
  allow-connections h323 to sip
  allow-connections sip to h323
  fax protocol cisco
 !
 !
 !
 voice class codec 1
  codec preference 1 g711ulaw
  codec preference 2 g729r8
 !
 interface Loopback0
  ip address 192.168.50.2 255.255.255.255
  h323-gateway voip interface
  h323-gateway voip id CUBE ipaddr 192.168.50.2 1719
  h323-gateway voip h323-id HQ
  h323-gateway voip bind srcaddr 192.168.50.2

 dial-peer voice 300 voip
  incoming called-number 3...
  codec g711ulaw
 !
 dial-peer voice 301 voip
  destination-pattern 3...
  session target ras
  codec g711ulaw

 gateway
  timer receive-rtp 1200
 !
 !
 !
 gatekeeper
  zone local CUBE cisco.com 192.168.50.2
  zone local UCME cisco.com outvia CUBE
  zone local UCM cisco.com
  zone prefix UCM 1... gw-priority 10 gk-trunk_2
  zone prefix UCME 3...
  zone prefix UCM 5... gw-priority 10 gk-trunk_2
  gw-type-prefix 1#* default-technology
  no shutdown
 
 HQ#show gatek end
 GATEKEEPER ENDPOINT REGISTRATION
 
 CallSignalAddr  Port  RASSignalAddr   Port  Zone Name TypeFlags
 --- - --- - - -
 192.168.10.30   53963 192.168.10.30   51666 UCM   VOIP-GW
 H323-ID: gk-trunk_1
 Voice Capacity Max.=  Avail.=  Current.= 0
 192.168.50.21720  192.168.50.253199 CUBE  H323-GW
 H323-ID: HQ
 Voice Capacity Max.=  Avail.=  Current.= 0
 192.168.50.41720  192.168.50.463228 UCME  VOIP-GW
 H323-ID: BR2
 E164-ID: 3001
 E164-ID: 3002
 Voice Capacity Max.=  Avail.=  Current.= 0
 Total number of active registrations = 3

 -
 debug h225 q931 from CUBE:
 HQ#debug h225 q931
 H.225 Q931 IE Details debugging is on
 HQ#
   Q931 Message IE Decodes
 Protocol Discriminator : 0x08
 CRV Length : 2
 CRV Value  : 0x0003
 Message Type   : 0x05: SETUP
  Bearer Capability: Length Of IE=3
  Data 8090A2
  Calling Party Number: Length Of IE=6
  Data 008135303031
  Called Party Number: Length Of IE=5
  Data 8033303031
  User-User: Length Of IE=193
  Data