RAS Binding

Hello,
 
I have tested, and when configuring the Gakeeper, and specifying the IP address for the first Zone Local, the Router binds the RAS signaling from the Gatekeerer Router to this IP address.
 
Although I have NOT configured the interface with "h323-gateway voip interface" or "h323-gateway voip bind srcaddr" on the GK Router.
 
Please can you confirm that the IP Address in the Zone Local configuration is used to Bind the RAS signaling leaving the Gatekeeper Router.

And the Interface h323 binding command are not necessary

Comments

  • This happens when you have simple topology and router isn't confused to select the default ethernet interface. However it's strongly recommended to use these commands.

    You will feel the need of these two commands specially 'h323-gateway voip bind srcaddr x.x.x.x' when you have multiple ethernet interfaces on complex topology like on IPIP-GW and you want to keep control the interfaces as a source of voip traffic. Have you labbed IPIP-GW recently? It will help you to understand the RAS traffics in deep dive.

  • Yes I have labbed the IPIPGW, and at this point I am at Gatekeeper with IPIPGW testings.


    On Tue, Dec 20, 2011 at 9:03 PM, MijanurRahman <[email protected]> wrote:

    This happens when you have simple topology and router isn't confused to select the default ethernet interface. However it's strongly recommended to use these commands.

    You will feel the need of these two commands specially 'h323-gateway voip bind srcaddr x.x.x.x' when you have multiple ethernet interfaces on complex topology like on IPIP-GW and you want to keep control the interfaces as a source of voip traffic. Have you labbed IPIP-GW recently? It will help you to understand the RAS traffics in deep dive.





    INE - The Industry Leader in CCIE Preparation
    http://www.INE.com

    Subscription information may be found at:
    http://www.ieoc.com/forums/ForumSubscriptions.aspx


  • One more point for you, you cannot configure the gateway h323-ID without the command 'h323-gateway voip interface' so it's a must if you want to register your gateway to GK.

    And for simple topology you really don't need the command 'h323-gateway voip bind srcaddr', you can take help from the example below:

    http://www.cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a00800a9a56.shtml#diag

    But in the lab sometime we need to define the command as there might be some requirement to source the h323 traffic from any particular interface.

    Hope it's clear now.

  • Thanks you very much


    On Tue, Dec 20, 2011 at 11:28 PM, MijanurRahman <[email protected]> wrote:

    One more point for you, you cannot configure the gateway h323-ID without the command 'h323-gateway voip interface' so it's a must if you want to register your gateway to GK.

    And for simple topology you really don't need the command 'h323-gateway voip bind srcaddr', you can take help from the example below:

    http://www.cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a00800a9a56.shtml#diag

    But in the lab sometime we need to define the command as there might be some requirement to source the h323 traffic from any particular interface.

    Hope it's clear now.




    INE - The Industry Leader in CCIE Preparation
    http://www.INE.com

    Subscription information may be found at:
    http://www.ieoc.com/forums/ForumSubscriptions.aspx


  • Hi Dotac,

     

    On GK you don't need "h323-gateway voip interface" or "h323-gateway voip bind srcaddr". GK RAS source address is always picked from local zone IP. However "h323-gateway voip interface" or "h323-gateway voip bind srcaddr" are used to define H323 GW RAS signaling address.

     

    Please differentiate between both.

     

    Regards,

    Mohd Baqari

Sign In or Register to comment.