Multiple SIP Transport Server using same IP but different port and limit of a maximum number of transport servers in the configuration.

[Guest]

Hi,

We have a use case to create about 50 transport servers by using the same IP but different ports. Is this feasible?  Is there any limit of a maximum number of transport servers in the configuration (of course we will have to provide the unique combination of IP and port)?

I found the documentation at the TBwiki and there is no mention of any limits.
https://docs.telcobridges.com/tbwiki/Toolpack:Creating_a_SIP_Transport_Server_SBC_A


Use Case:
1. We are going to have a sip trunk between us and a customer. Our customer is going to send the traffic to us (from single IP) for their 50 sub-customers. And they don’t have the capability to use prefixes. Our customer wants to dedicate a SIP port for each  customer as following:

• Sub Customer   PORT
• Sub-Customer1 =>5061
• Sub-Customer2 =>5062
• Sub-Customer3 =>5063

2. In ProSBC, under SIP STACK, I have to create multiple transport Servers having the different port numbers.
• TS_VOIP0_5061
• TS_VOIP0_5062
• TS_VOIP0_5063
• etc...

3. Once the transport servers have been created, I will have to utilize them while creating the NAP.

Please confirm if this is the correct way of configuration for the given use case.

[Guest]

Hello,

Yes, the way you are configuring the ProSBC to use the different local port and associate them with the NAP explicitly is correct.
The maximum Transport Server is 96, so I guess you are OK to go.

[AndrzejP]

Hi,

in SIP stack configuration group Advanced there is an option:

Code:

Advanced Transport Servers configuration
Tip("Enable advanced SIP Transport servers configuration (allowing more than 96 transport servers by grouping them into SIP SAPs).")

1. What is the limit for TS when using SIP SAPs?
2. How should we group Transport Servers in SIP Service Access Points ?

Our use case is connecting to cloud service (Genesys Cloud CX) that has single IP and port for multiple accounts (NAPs on our side) and we need prosbc to be able to properly assing NAP to a call. So we need unique combination of ip and port for each NAP.