Comments on RM:

• RESMAN should never contain a route with more than 16 sectors.
• Only WAN sectors are supported for bandwidth calculation and not LAN sectors.
• Each RESMGMT1 from AMO GKTOP must contain the AMO ZAND PKNNO under the PKNNO parameter, i.e. this is not the AMO KNDEF entry.
• IP TRUNKING is not supported.
• Network-wide configuration is extremely time intensive and if an incorrect sector is received from a partner system DMC is not switched (see MSC15245 for an alternative simpler configuration).
• When a DMC connection is made the bandwidth is not reduced if the CODEC is of a lower quality until the call is disconnected. If the bandwidth is more i.e. a higher bandwidth is used for the DMC connection the value is increased normally.
• MOBHFA is supported. Upon successful logon the cluster ID of the guest station is also stored. Bandwidth calculation will take into account the path from the guest station to the home gateway and then from the home gateway to the called party. DMC can also increase the bandwidth dependant on which CODEC is used for the master connection.
• The bandwidth is always calculated as configured i.e. from host system in direction of the AP. If the call is between two APs the routes are overlaid (compared) to establish the true route.
• AMO SBCSU parameter IPCODEC must be configured for HFA phones to calculate the bandwidth correctly.
• When using AMO KCSU no bandwidth reservation will be made during ringing state (first by connect).
• Each gateway should be connected to a LAN sector (not directly to WAN!).