Multiple Listening/Local Port on BSS

[skb007]

1. Brekeke Product Name and Version:3.5.2

2. Java version:1.8

3. OS type and the version:RHEL 1.8

4. UA (phone), gateway or other hardware/software involved:Multiple

5. Your problem:
We are currently using port 5060 but one of our customer wants to use port 5075. How can I configure the Brekeke to listen on 5060 as well as 5075.

I tried entering 5060,5075 in the SIP-->Local Port it does not take that, it is only accepting integer values.

Please help.

[Tata]

There is no way to open multiple listening ports.

To do so, you need to setup one more Brekeke SIP Server at another machine which listens on the port 5075, and then forwards packets to the SIP Server which listens on the port 5060.

[skb007]

Appreciate your response. I wont be able to do what you have suggested.

Is there any way to use multiple IP's on the same BSS. For example, I want to receive leg a on one IP and outgoing leg-B should use second IP.

customer------> BSS-IP1, BSS-IP2 -----> Carrier.

[Tata]

It is possible.
Add one more interface IP address to the OS, and then define it with the customer's IP address pattern at SIP Server's [Configuration]->[Network] settings.

Also you might need to use OS's route command to specify peer of new interface IP address and remote IP address prefix.

[skb007]

Actually, we have to send the leg-B to the same IP address from where leg-A is originating. So Ip address pattern option is not going to work for us.

I have already defined 2 IP address on the OS and I tried to the following but it did not work, it keeps on sending the leg-b packets from 192.168.2.56. Even though SIP headers are changed to 192.168.2.57.

Matching Patterns

$addr = 192.168.2.180 $request = ^INVITE To = sip:(.+)@ web.webget("https://192.168.2.100/geyValue.php?parm1 = %1") = (.+)

Deploy Patterns

To = sip:%2@192.168.2.180 $b2bua = false $rtp = false $ifsrc = 192.168.2.56 $ifdst = 192.168.2.57

sipp (192.168.2.180)---->BSS(192.168.2.56 and 192.168.2.57) ---->192.168.2.180

[james]

Because UAC and UAS are using same IP address, the above deployment will not meet your requirement.

My idea is use TCP for UAC side, and UDP for UAS side. This is because they can bind to different interface IP address.

For example..
net.sip.tcp.bind.interface = 192.168.2.56
net.bind.interface = 192.168.2.57

[skb007]

Thanks and appreciate your response.