Throughpacket; Registration With Endpoints - AudioCodes Mediant 1000 User Manual

H.323 User's Manual
8.5.3

Registration with Endpoints

The gateway registers with the Gatekeeper using the numbers defined in the 'Trunk Group
Table' screen (normally used with FXS modules).
To register with endpoints, take these 2 steps:
Don't configure the Registration Prefixes Table.
1.
Set the GWRegistrType parameter according to your requirements:
2.
•
E.164 [0] = The gateway registers the endpoints using E.164 format.
•
H323-ID [1] = The gateway registers the endpoints with the port IDs specified in
the 'H.323 Port ID' table (if the 'H.323 Port ID' table isn't configured, the
endpoints are represented as strings). In this mode don't configure the
H323IDString parameter (if you do, the gateway only registers with H323IDString
and the H.323 Port IDs / endpoints are ignored).
•
E.164 and H323-ID [2] = The gateway registers the endpoints using E.164 and
H.323-ID formats. In this mode the H323IDString (if defined) is added to the
Registration Request (once); if not defined, each endpoint registers twice, in
E.164 format and H.323-ID format (using the 'H.323 Port ID' table or, if this table
isn't defined, as a string).
•
NPI/TON from Table [3] = N/A in this mode.
•
NPI/TON and H323-ID [4] = N/A in this mode.
For detailed information on the 'H.323 Port ID' table, refer to Section
8.6

ThroughPacket™

The gateway supports a proprietary method to aggregate RTP streams from several
channels to reduce the bandwidth overhead caused by the attached Ethernet, IP, UDP and
RTP headers, and to reduce the packet / data transmission rate. This option reduces the
load on network routers and can typically save 50% (e.g., for G.723) on IP bandwidth.
ThroughPacket™ is accomplished by aggregating payloads from several channels that are
sent to the same destination IP address into a single IP packet.
ThroughPacket™ can be applied to the entire gateway or, using IP Profile, to specific IP
destinations (refer to Section
enabled on both gateways.
To enable ThroughPacket™ set the parameter 'RemoteBaseUDPPort' to a nonzero value.
Note that the value of 'RemoteBaseUDPPort' on the local gateway must equal the value of
'BaseUDPPort' of the remote gateway. The gateway uses these parameters to identify and
distribute the payloads from the received multiplexed IP packet to the relevant channels.
In ThroughPacket™ mode, the gateway uses a single UDP port for all incoming
multiplexed packets and a different port for outgoing packets. These ports are configured
using the parameters 'L1L1ComplexTxUDPPort' and 'L1L1ComplexRxUDPPort'.
When ThroughPacket™ is used, Call statistics aren't available (since there is no RTCP
flow).
Version 5.0
5.5.5.3 on page 110). Note that ThroughPacket™ must be
265
8. Telephony Capabilities
5.5.7.1 on page 114.
December 2006