Forum Discussion
ashley_sauls_67
Mar 23, 2007Historic F5 Account
persistance on sip traffic fails when the bye message comes
So we’re giving it a shot on 9.4
some bug near elseif that I could not work out caused me to break it into 2 separate rules
sipRule_1
when SIP_REQUEST {
set method [SIP::met...
Colin_Walker_12
Apr 02, 2007Historic F5 Account
First of all, let's try and put this back into a single rule for clarity's sake. Second, let's add a little logic to make sure that we're trying to delete a persistence record that actually exists. Lastly, let's be sure we're using a valid persistence method to start with (uie rather than sip).
In the end, I think you'll end up with something close to:
when SIP_REQUEST {
set method [string tolower [SIP::method] ]
log local0.info "SIP Method is: $method"
if { ($method equals "request") or ($method equals "invite") } {
persist uie [SIP::call_id]
} elseif { $method equals "bye" } {
if { [string length [persist lookup uie [SIP::call_id] node] ] > 0 } {
persist delete uie [SIP::call_id]
}
}
}
HTH,
Colin
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects