TRANSip Resources
TRANSip in the HDX or the
SLICE 2100 consists of:
- TRANSip Software located in the controller board
- Includes 100 IP Registerant entries per HDX shelf or SLICE 2100 unit
- Optional blocks of 100 IP registrants can be
purchased (up to 1000 subscribers per shelf)
- TRANSip Media Services Circuit (MSC)
board for the HDX (equivalent functionality is embedded in SLICE 2100)
- Includes TRANSip Media Gateway
Functionality
- Optional TRANSip MoIP/FoIP Engines
Resource Planning
Common resources in the
HDX and SLICE 2100 consist of:
1) Ports
2) Timeslots
3) IP Registerants
Ports and timeslots are
explained in the previous section. There are 1000 ports in the HDX and SLICE 2100. There are 512 timeslots in each HDX shelf and SLICE 2100 unit. The amount
of timeslots per HDX shelf in a system with more than 8 shelves will change based on the total number of shelves.
There are up to 1000 IP
registrants in each HDX shelf or SLICE 2100 unit. These registrants do not use any ports unless they are active, mean-ing in a call state. These IP
registrants only use timeslots if they need to access the voice related services like access to TDM or custom an-nouncements offered by HDX or SLICE
2100.
The timeslots and ports that are used for IP calls are located in the MSC board. Therefore, the number of timeslots and ports that
are needed for IP calls should be assigned to the MSC board. One MSC board can have up to 128 timeslots. Additional boards should be added to the system if
more timeslots (i.e. IP to TDM conversions) are needed.
Below are two examples to further clarify the shared resources in the HDX and SLICE
2100.
IP to IP Call

In this example, an IP phone calls another IP phone using HDX as the call controller.
These phones are registered in the HDX, thus they oc-cupy 2 of the possible 1000 entries in this HDX shelf. They do not occupy any port until they call each
other. The moment they call each other, each of them occupies a port on the MSC board. However, since there is no IP to TDM conversion, no timeslots are
used.
Total resources used in this example:
- Ports = 2 (on the MSC Board during the
call)
- Timeslots = 0 (no TDM connection)
- IP Registrants = 2 (each IP phone is registered to the
HDX)
IP to TDM Call

In this example,
an IP phone calls an analog phone using TRANSip HDX as the call controller and media gateway. The IP phone is registered to TRANSip and occupies 1 of the
possible 1000 entries in the HDX shelf. The moment the IP phone calls the analog phone or vice versa, a timeslot is used in the MSC board for media gateway
functionality.
The total resources used in this example:
- Ports = 2 (1 port on the MSC board and 1 port for
the analog line)
- Timeslots = 2 (1 timeslot on the MSC board and 1 timeslot on the analog line)
- IP Registrant = 1
(only 1 IP phone is registered to the HDX)
The resource planning might be complicated due to the
number of variants. At REDCOM, we will be more than happy to help with resource planning if our customers have any questions or concerns.
IP User Registration
TDM circuit-switched
phones and other TDM equipment are physically connected to the HDX or SLICE 2100. This gives some physical as-surance that the device is
authorized.
An IP telephone is not connected physically to the HDX or SLICE 2100. Rather, it simply sends a message to the TRANSip's SIP
Call Controller requesting to be "registered". Once an IP phone is successfully registered, the TRANSip's SIP Call Controller may dispatch
calls to it and ac-cept requests for service from it.
Because the IP phones are not physically connected to the TRANSip's SIP Call
Manager, it must ensure the IP phone is, indeed, an authorized device, and not one that is masquerading for the purpose of unauthorized use of TRANSip's
services. This is accomplished by setting the phone to recognize the IPv4 or IPv6 address of the HDX shelf or SLICE 2100 unit and also assigning an optional
pre-arranged password. The SIP user of the IP phone and the same pre-arranged password are entered into the TRANSip's IP Registrant
table.
Registration validates the existence of the IP phone. When the IP phone is "idle", it is merely known to the
TRANSip's SIP Call Manager—it uses no additional resources in the HDX or SLICE 2100.