Change Far IP Transport Address for UDP Path
....................................................................................................................................................................................................................................
Purpose
This section contains the procedure for changing the IP address and/or
UDP port of the far end of a UDP path.
When to use
Use this procedure when the IP transport address or the UDP port
number of the far end office changes, and a UDP path exists to the
old address.
Related information
Refer to 235-118-258, Recent Change Reference, for information on
the RC/V system.
Refer to the 235-600-700/750, Input/Output Messages manuals for
additional information on the Input and Output commands.
Admonishments
None.
Before you begin
Required Tools
• Supplemental Trunk Line Workstation (STLWS) or Recent
Change and Verify (RC/V) terminal
• Access to RC/V Menu Interface
Required Material
• The 5ESS
®
switch must be running a 5E16.2 FR5 software
release with UDP Transport for SIP software.
Required Information
• New IP address and UDP port for SIP signaling at far office
• UDP Path number of existing UDP Path to far office
Required Conditions
• None
Procedure
............................................................................................................................................................
1
Examine the PKTGRP/5219 records to determine whether there is a
SIP Packet Group assigned to the UDP path in question. If there is no
SIP Packet Group assigned to the UDP Path, proceed to step 6.
............................................................................................................................................................
2
If a SIP Packet Group is assigned to the UDP path, examine the
TKGRP/5202 office records to determine whether there is a trunk
Provisioning
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
5-129