Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+SIP\s+Caller\s+ID\s+persistency\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+SIP\s+Caller\s+ID\s+persistency\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [lvs-users] SIP Caller ID persistency (score: 1): Author: Mark Brooks <mark@xxxxxxxxxxxxxxxx>; Date: Thu, 29 Dec 2011 12:16:04 +0000; Hi Kumar, its been a while since I have looked at this and most of my notes are on my desk at work :-), but I think you need to enable one packet scheduling to get the sip call id persistence to work; /html/lvs-users/2011-12/msg00048.html (11,070 bytes)
2. [lvs-users] SIP Caller ID persistency (score: 1): Author: Kumar Swamy <kswamy@xxxxxxxxxxxxx>; Date: Thu, 29 Dec 2011 03:34:04 -0800; Hi, I have configured servers 10.11.20.31 and 10.11.20.32 as part of a SIP service 10.11.20.117 in direct server return mode. Here is the output of "ipvsadm-save -n" command output. -A -u 10.11.20.11; /html/lvs-users/2011-12/msg00047.html (9,193 bytes)

Current List: 1 - 2
Page: [1]