For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

satish_txt_2254's avatar
satish_txt_2254
Icon for Cirrus rankCirrus
May 13, 2017

SIP proxy BYE messages handling

We have multiple SIP proxy behind F5 load balancer and we are using 

Record-Route
to keep F5 in path but i have notice my 
ACK
message was bouncing back and not going through in that case i add following iRule which fixed issue but now my BYE message is not getting handle correctly

when SIP_REQUEST_SEND {
    SIP::header remove "Route" 
    }

In BYE message i am seeing it has wrong R-URI and it has F5 SelfIP address in BYE instead of End-User 

BYE sip:tester@F5-SelfIP:41623 SIP/2.0

I have notice my 

Contact header
has that address. anyone having this issue?

We are using 

Automap
for SNAT

application delivery
BIG-IP
LTM

2 Replies

  • Nazir_52641's avatar
    Nazir_52641
    Icon for Cirrus rankCirrus
    May 19, 2017

    Hi Satish,

     

    Please share the SIP message flow to give exact solution.

     

    In clients normally Request-URI for in-dialog request ACK/BYE will be framed from Contact header of 200 OK of SIP INVITE. If the Contact of 200 OK is altered in F5 then you should avoid manipulating Contact header.

     

    Thanks

     

    Syed Nazir