Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ipvs\:\s+handle\s+outgoing\s+messages\s+in\s+SIP\s+persistence\s+engine\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ipvs\:\s+handle\s+outgoing\s+messages\s+in\s+SIP\s+persistence\s+engine\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: ipvs: handle outgoing messages in SIP persistence engine (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Mon, 21 Mar 2016 23:08:30 +0200 (EET); Hello, I see, ok ok In OPS mode the connection templates are alone. May be PE-SIP can modify the ct timer depending on the SIP method, session timer, I don't know. Even BYE can be lost, so we should; /html/lvs-devel/2016-03/msg00020.html (17,838 bytes)
2. Re: ipvs: handle outgoing messages in SIP persistence engine (score: 1): Author: Marco Angaroni <marcoangaroni@xxxxxxxxx>; Date: Mon, 21 Mar 2016 16:50:03 +0100; Hello, please check my responses / comments inline. For architectural aspects, in short: - In my opinion it's reasonable that IPVS handles only SIP traffic and not media traffic. RTP packets typicall; /html/lvs-devel/2016-03/msg00019.html (47,355 bytes)
3. Re: ipvs: handle outgoing messages in SIP persistence engine (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sat, 19 Mar 2016 23:27:53 +0200 (EET); Hello, From point 2 looks like you are balancing SIP calls? How do you route the media packets? It is also possible that response is sent to different client port, see B.2 below. Agreed, IPVS is not; /html/lvs-devel/2016-03/msg00018.html (37,777 bytes)
4. ipvs: handle outgoing messages in SIP persistence engine (score: 1): Author: Marco Angaroni <marcoangaroni@xxxxxxxxx>; Date: Tue, 08 Mar 2016 18:17:25 +0100; Hello, Im trying to use IPVS as a high performance load-balancer with minimal SIP-protocol awareness (routing based on Call-ID header). I started from the patch by Simon Horman as described here: htt; /html/lvs-devel/2016-03/msg00015.html (24,985 bytes)

Current List: 1 - 4
Page: [1]