Sorry all, I just needed to set reply_to_via=1. I should have checked the cookbook before posting - now it works.

Tim

On 3/22/07, Tim Madorma tmadorma@gmail.com wrote:

Hi,

I have an OpenSER behind a BIG IP load balancer. The scenario is as follows:

1. The UAC will initiate the call with an INVITE that has the REQ URI

set to the IP of the BIG IP.

2. The OpenSER has an alias configured for the IP address of the BIG

IP so it receives the incoming INVITE, but when it sends a 100 response, it does not send it to the UAC address that is specified in the VIA header, rather it sends it to the source IP (which is the IP of the BIG IP load balancer). This is undesirable.

3. After the UAS receives the proxied INVITE, it responds with a 100,

then answers with a 200.

4. When the OpenSER receives the 100, it forwards this back to the BIG

IP load balancer! First, I am surprised that it fowards a 100 at all, and second it is undesirable to send any responses to the BIG IP load balancer since the via header indicates the IP of the UAC.

5. When the OpenSER receives the 200, it forwards it back to the BIG

IP also.. again, I don't know why it isn't sending to the IP address of the via - which is that of the UAC.

Any suggestions would be most helpful.

Here are my related openser.cfg settings:

# LOCAL IP ADDRESS AND PORTS listen=65.185.232.62:5061 listen=65.185.232.62:5062 listen=65.185.232.62:5063

# IP ADDRESS AND PORTS OF THE BIG IP LOAD BALANCER alias=65.185.233.104:5061 alias=65.185.233.104:5062 alias=65.185.233.104:5063

thanks, Tim

Hi!

Probably the Via: header contains the "rport" parameter which tells openser to send the response back symmetrically (the the IP address it receivd the request, not to the IP address in the Via header). For this it would be necessary to have an "unforce_rport" function which openser does not have yet.

regards klaus

Tim Madorma wrote:

Hi,

I have an OpenSER behind a BIG IP load balancer. The scenario is as follows:

1. The UAC will initiate the call with an INVITE that has the REQ URI

set to the IP of the BIG IP.

2. The OpenSER has an alias configured for the IP address of the BIG

IP so it receives the incoming INVITE, but when it sends a 100 response, it does not send it to the UAC address that is specified in the VIA header, rather it sends it to the source IP (which is the IP of the BIG IP load balancer). This is undesirable.

3. After the UAS receives the proxied INVITE, it responds with a 100,

then answers with a 200.

4. When the OpenSER receives the 100, it forwards this back to the BIG

IP load balancer! First, I am surprised that it fowards a 100 at all, and second it is undesirable to send any responses to the BIG IP load balancer since the via header indicates the IP of the UAC.

5. When the OpenSER receives the 200, it forwards it back to the BIG

IP also.. again, I don't know why it isn't sending to the IP address of the via - which is that of the UAC.

Any suggestions would be most helpful.

Here are my related openser.cfg settings:

# LOCAL IP ADDRESS AND PORTS listen=65.185.232.62:5061 listen=65.185.232.62:5062 listen=65.185.232.62:5063

# IP ADDRESS AND PORTS OF THE BIG IP LOAD BALANCER alias=65.185.233.104:5061 alias=65.185.233.104:5062 alias=65.185.233.104:5063

thanks, Tim

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users