Hello Liviu,
Yes, that correct. Right now each node in cluster have own vip from
keepalived on LAN side.
The issue how to specify correct vip in case of failover, so if node 2
fail and node 2 vip was relocated to node 1. All sessions should be
process on node 1 and
append_hf("Path: <sip:$fU@MAIN_VIP:5060;transport=udp>\r\n"); should
have correct ip's. Same with rtpengine offer
rtpengine_offer("replace-origin replace-session-connection
in-iface=external out-iface=internal media-address=$avp(media_addr)
RTP/AVP ICE=remove") where need introduce media-address to specify
correct vip ip.
Can you exapand on m4 ? I never used the templating.
Might db avp to predefine cluster nodes vip ip, not sure.
volga629
On Thu, Aug 2, 2018 at 10:50 AM, Liviu Chircu <li...@opensips.org>
wrote:
Hi Volga,
If I understood your problem correctly, one idea would be to use m4
over opensips.cfg and define a different MAIN_VIP variable for each
of your three servers:
append_hf("Path: <sip:$fU@MAIN_VIP:5060;transport=udp>\r\n");
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09.07.2018 07:34, volga...@networklab.ca wrote:
Hello Everyone,
I have work around on this issue
# Work arround for github issue #1109
append_hf("Path: <sip:$fU@listen ip:5060;transport=udp>\r\n"
Right now we use 3 node cluster with 3 vips in active/active mode
I need some idea how to determine path header listen ip address from
3 vips.
volga629
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
