Forum Discussion

Amit_Grover_171's avatar
Amit_Grover_171
Icon for Nimbostratus rankNimbostratus
Jul 08, 2015

Is it possible to add a pool IP and port as record route instead of Vistrual address IP using SIP profile

Hi,

 

I am trying to use F5 as reverse SIP proxy.

 

Client A --> F5-->unix server-->F5--> Client B

 

Desgin is like f5 will initiate two connection (inbound and outbound) for communication in between client A and clinet B. So i want to know Is it possible to add a pool IP and port as record route instead of Vistrual address IP using SIP profile.

 

/Regards Amit Grover

 

6 Replies

  • Vernon_97235's avatar
    Vernon_97235
    Historic F5 Account

    You'll need to use an iRule to do this. The sip profile has an option to insert the Record-Route header. You would want to disable this (it's disabled by default) on the sip child profile applied to the Virtual Server. Then add an iRule like this:

    when SIP_REQUEST_SEND {
        SIP::header insert Record-Route [LB::server addr]
    }
    
    • Amit_Grover_171's avatar
      Amit_Grover_171
      Icon for Nimbostratus rankNimbostratus
      Thanks Vernon for your response. Can you please let me understand how Dialog Aware and community works in SIP persistance.
  • You'll need to use an iRule to do this. The sip profile has an option to insert the Record-Route header. You would want to disable this (it's disabled by default) on the sip child profile applied to the Virtual Server. Then add an iRule like this:

    when SIP_REQUEST_SEND {
        SIP::header insert Record-Route [LB::server addr]
    }
    
    • Amit_Grover_171's avatar
      Amit_Grover_171
      Icon for Nimbostratus rankNimbostratus
      Thanks Vernon for your response. Can you please let me understand how Dialog Aware and community works in SIP persistance.
  • Thanks Vernon, But I already review these solution guide .

     

    We are facing issues, when we want to persist SIP traffic in between two different legs (inbound & outbound) on basis of dialogue aware.

     

    idly call ID in between client A-- >f5-->Unix server will be different and from Unix server-->f5-->Client B will be different.

     

    I am not able to figure out how can I persist two legs with community and dialogue aware option in SIP profile.

     

    /Regards Amit Grover