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...
Shay_Ben-David1
Nimbostratus
Feb 15, 2009i used the same irule:
when SIP_REQUEST {
set method [string tolower [SIP::method] ]
log local0.info "SIP Method is: $method"
if { ($method equals "request") or ($method equals "invite") } {
return
} elseif { $method equals "BYE" } {
if { [string length [persist lookup uie [SIP::call_id] node] ] > 0 } {
persist uie [SIP::call_id] 5
}
}
}
only i am updating the persist table when BYE is sent, but i have another irule for the incoming who sent the returning SIP connection to the correct originate server from inside:
when SIP_REQUEST {
pool mypool
set id "[persist lookup sip [SIP::call_id]]"
log local0.alert "ID found in lookup is: $id"
if { [llength $id] } {
log local0.alert "In if select pool"
return
}
set id "[SIP::call_id] any virtual"
set sessionInfo [session lookup uie $id]
log local0.alert "Session information found is: $sessionInfo"
if { [llength $sessionInfo] } {
log local0.alert "Choosing member acording to session info"
pool mypool member $sessionInfo
}
}
Problem is that only one BYE is being forward to one server, other BYE that belong to the next server that originate SIP session is being sent to the LTM but does not forward to the server.
help would be appreciated here.
Thanks
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