Forum Discussion
6 Replies
- Vernon_97235Historic 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_171NimbostratusThanks Vernon for your response. Can you please let me understand how Dialog Aware and community works in SIP persistance.
- VernonWellsEmployee
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_171NimbostratusThanks Vernon for your response. Can you please let me understand how Dialog Aware and community works in SIP persistance.
- VernonWellsEmployee
This document describes the SIP profile settings:
This document provides a more complete description of using LTM with SIP:
Have you had a chance to look these over?
- Amit_Grover_171Nimbostratus
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