Hi
I currently have a single SER server using MySQL for data storage. Due to the number of users I now have and to help redundancy I want to setup another SER server.
I have search the web and have not been able to find a tutorial on this so I hope someone on this list can help.
I need the SER servers to at least know about the location of clients registered with each server. Therefore can I point both servers at the same MySQL and for them to share the data?
Are there any issues around this strategy? Is there another way to accomplish what I want?
Regards
Jon
I was thinking about this myself the other day. I don't think this should be a problem. Even if a client registered with a different server, SER will still use the same contact information to get to the client. So it shouldn't matter at all.
You should be able to setup many SER servers and have them all look at the same database.
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Jon Farmer Sent: Monday, September 18, 2006 1:28 PM To: SER Mailing List Subject: [Serusers] Scaling SER
Hi
I currently have a single SER server using MySQL for data storage. Due to the number of users I now have and to help redundancy I want to setup another SER server.
I have search the web and have not been able to find a tutorial on this so I hope someone on this list can help.
I need the SER servers to at least know about the location of clients registered with each server. Therefore can I point both servers at the same MySQL and for them to share the data?
Are there any issues around this strategy? Is there another way to accomplish what I want?
Regards
Jon
Natambu Obleton writes:
I was thinking about this myself the other day. I don't think this should be a problem. Even if a client registered with a different server, SER will still use the same contact information to get to the client. So it shouldn't matter at all.
how about if client is behind nat?
-- juha
mediapoxy'll handle it.
On 9/19/06, Juha Heinanen jh@tutpro.com wrote:
Natambu Obleton writes:
I was thinking about this myself the other day. I don't think this should be a problem. Even if a client registered with a different server, SER will still use the same contact information to get to the client. So it shouldn't matter at all.
how about if client is behind nat?
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
It won't. Have a look at this FAQ: http://www.iptel.org/faq/how_can_i_get_load_balancing_failover_with_ser
It is adapted from a post I made to serdev a while back. It can most certainly be improved, but I decided to throw it up there instead of trying to answer in this thread... g-)
Andrey Kuprianov wrote:
mediapoxy'll handle it.
On 9/19/06, Juha Heinanen jh@tutpro.com wrote:
Natambu Obleton writes:
I was thinking about this myself the other day. I don't think this
should be
a problem. Even if a client registered with a different server,
SER will
still use the same contact information to get to the client. So it
shouldn't
matter at all.
how about if client is behind nat?
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I'll keep that in mind then :)
On 9/19/06, Juha Heinanen jh@tutpro.com wrote:
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Ohh.. I thought the keepalives would allow other ip address, than the one that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Different kind of NATs have different logic, but you have to assume worst (and it quite popular :))
-----Original Message----- From: Natambu Obleton [mailto:nobleton@fasttrackcomm.net] Sent: Tuesday, September 19, 2006 12:26 PM To: Vitaly Nikolaev ; serusers@iptel.org Subject: RE: [Serusers] Scaling SER
Ohh.. I thought the keepalives would allow other ip address, than the one that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Actually it depends on the NAT implementation. There are four generally known/defined types (in STUN), but a lot of variants. When we talk about the NAT problem, we always talk about the worst-case, which is a symmetric NAT, i.e. only packets from src ipA:portB will be allowed through and only if a previous packet has been going out to dst ipA:portB not longer ago than a defined time-out. Some NATs have timeout of 60 minutes, others (could be) as low as 30 sec. g-)
Natambu Obleton wrote:
Ohh.. I thought the keepalives would allow other ip address, than the one that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I bet an Anycast setup with multiple servers having the same ip address pointing to the same Mysql database would work. I have done it with mail servers and dns servers.
http://en.wikipedia.org/wiki/Anycast#Reliability_of_anycast
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Tuesday, September 19, 2006 11:55 PM To: Natambu Obleton Cc: 'Vitaly Nikolaev '; serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Actually it depends on the NAT implementation. There are four generally known/defined types (in STUN), but a lot of variants. When we talk about the NAT problem, we always talk about the worst-case, which is a symmetric NAT, i.e. only packets from src ipA:portB will be allowed through and only if a previous packet has been going out to dst ipA:portB not longer ago than a defined time-out. Some NATs have timeout of 60 minutes, others (could be) as low as 30 sec. g-)
Natambu Obleton wrote:
Ohh.. I thought the keepalives would allow other ip address, than the one that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
There are stateless or statefull Sip proxy operational modes, second is what I use and it require same server that send request received response.
Why do you need all this mess btw?
If you just have simple SER server it can handle up to A LOT of customers (100k?), for redundancy you can use heartbeat with t_replicate in ser.
If you use rtpproxy, then just use distributed rtpproxy, get few linux boxes install rtpproxy on it and let ser/nathelper do redundancy/failover between them for RTP traffic, all this feature (except heartbeat) are exist in ser
But if you want to have different SERs in different locations, and have customers distributed between them, you have to have "smart" something that will route call between them (b2bua of course)
-----Original Message----- From: Natambu Obleton [mailto:nobleton@fasttrackcomm.net] Sent: Wednesday, September 20, 2006 9:47 AM To: 'Greger V. Teigre' Cc: Vitaly Nikolaev ; serusers@iptel.org Subject: RE: [Serusers] Scaling SER
I bet an Anycast setup with multiple servers having the same ip address pointing to the same Mysql database would work. I have done it with mail servers and dns servers.
http://en.wikipedia.org/wiki/Anycast#Reliability_of_anycast
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Tuesday, September 19, 2006 11:55 PM To: Natambu Obleton Cc: 'Vitaly Nikolaev '; serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Actually it depends on the NAT implementation. There are four generally known/defined types (in STUN), but a lot of variants. When we talk about the NAT problem, we always talk about the worst-case, which is a symmetric NAT, i.e. only packets from src ipA:portB will be allowed through and only if a previous packet has been going out to dst ipA:portB not longer ago than a defined time-out. Some NATs have timeout
of 60 minutes, others (could be) as low as 30 sec. g-)
Natambu Obleton wrote:
Ohh.. I thought the keepalives would allow other ip address, than the
one
that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev
Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first
hit
SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some
references
to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Yes, I agree. Many talk about redundancy and failover necessary for 6-digit subscribers (I wouldn't sleep well with one box running 100k subscribers...), but few actually have that subscriber base and can do with the setup are describing (either linux HA or vrrp as I mentioned in my previous post). BTW, you don't need a B2BUA for routing calls between ser servers, everything can be done in ser.cfg. g-)
Vitaly Nikolaev wrote:
There are stateless or statefull Sip proxy operational modes, second is what I use and it require same server that send request received response.
Why do you need all this mess btw?
If you just have simple SER server it can handle up to A LOT of customers (100k?), for redundancy you can use heartbeat with t_replicate in ser.
If you use rtpproxy, then just use distributed rtpproxy, get few linux boxes install rtpproxy on it and let ser/nathelper do redundancy/failover between them for RTP traffic, all this feature (except heartbeat) are exist in ser
But if you want to have different SERs in different locations, and have customers distributed between them, you have to have "smart" something that will route call between them (b2bua of course)
-----Original Message----- From: Natambu Obleton [mailto:nobleton@fasttrackcomm.net] Sent: Wednesday, September 20, 2006 9:47 AM To: 'Greger V. Teigre' Cc: Vitaly Nikolaev ; serusers@iptel.org Subject: RE: [Serusers] Scaling SER
I bet an Anycast setup with multiple servers having the same ip address pointing to the same Mysql database would work. I have done it with mail servers and dns servers.
http://en.wikipedia.org/wiki/Anycast#Reliability_of_anycast
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Tuesday, September 19, 2006 11:55 PM To: Natambu Obleton Cc: 'Vitaly Nikolaev '; serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Actually it depends on the NAT implementation. There are four generally known/defined types (in STUN), but a lot of variants. When we talk about the NAT problem, we always talk about the worst-case, which is a symmetric NAT, i.e. only packets from src ipA:portB will be allowed through and only if a previous packet has been going out to dst ipA:portB not longer ago than a defined time-out. Some NATs have timeout
of 60 minutes, others (could be) as low as 30 sec. g-)
Natambu Obleton wrote:
Ohh.. I thought the keepalives would allow other ip address, than the
one
that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev
Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first
hit
SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some
references
to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Remember that the SIP protocol has a requirement on both transactions and dialogs (if you do accounting) to go through the same server. If you have stateless proxies, no problem, but we are normally talking about stateful proxies. I know people have experiemented with vrrp. http://sourceforge.net/projects/vrrpd/
You would probably implement the peers with either usrloc-cl against a mysql cluster or by using t_replicate. g-)
Natambu Obleton wrote:
I bet an Anycast setup with multiple servers having the same ip address pointing to the same Mysql database would work. I have done it with mail servers and dns servers.
http://en.wikipedia.org/wiki/Anycast#Reliability_of_anycast
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Tuesday, September 19, 2006 11:55 PM To: Natambu Obleton Cc: 'Vitaly Nikolaev '; serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Actually it depends on the NAT implementation. There are four generally known/defined types (in STUN), but a lot of variants. When we talk about the NAT problem, we always talk about the worst-case, which is a symmetric NAT, i.e. only packets from src ipA:portB will be allowed through and only if a previous packet has been going out to dst ipA:portB not longer ago than a defined time-out. Some NATs have timeout of 60 minutes, others (could be) as low as 30 sec. g-)
Natambu Obleton wrote:
Ohh.. I thought the keepalives would allow other ip address, than the one that originally opened the connections, to send in.
I guess that wouldn't be very secure would it.... :)
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vitaly Nikolaev Sent: Tuesday, September 19, 2006 8:53 AM To: serusers@iptel.org Subject: RE: [Serusers] Scaling SER
To extend Juha's info:
Only SER server that just received SIP packet from SIP device (either register or keepalive) can send something back in case of NAT
For example you have SER1 and SER2, client A registered on SER1 and client B on SER2, when client B sends call to client A it will first hit SER2 then SER2 to according to replicated location table will try to send it to client A straight and fail in case client A behind the nat (which is quite often in real world)
Trick is to teach SER2 to forward call to SER1 when needed, it can be done when you use b2bua that looks to same location table for example (ser need to be taught to place its IP also in same table).
Can not give you exact howto but can give (out of list) some references to commercial software if interested.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, September 19, 2006 8:52 AM To: Andrey Kuprianov Cc: serusers@iptel.org Subject: Re: [Serusers] Scaling SER
Andrey Kuprianov writes:
mediapoxy'll handle it.
mediaproxy does not forward sip requests.
-- juha _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
It shouldn't matter because the location and the port that the keep-alives are keeping open should be the same.
Natambu Obleton Network Engineer FastTrack Communications nobleton@fasttrackcomm.net (970) 247-3366 office (970) 247-2426 fax
-----Original Message----- From: Juha Heinanen [mailto:jh@tutpro.com] Sent: Monday, September 18, 2006 10:57 PM To: Natambu Obleton Cc: 'Jon Farmer'; 'SER Mailing List' Subject: RE: [Serusers] Scaling SER
Natambu Obleton writes:
I was thinking about this myself the other day. I don't think this should
be
a problem. Even if a client registered with a different server, SER will still use the same contact information to get to the client. So it
shouldn't
matter at all.
how about if client is behind nat?
-- juha
Hi,
I am nowhere near at your level, i mainly perform experimentations on my own behalf. But I read alot. I have read about the sip router being able to load a 1,000,000 location records within 256MB of memory and that you may need extra memory for active calls and message processing. Calling rate should be considered with regard to CPU power for amount of subscribers.
So, final recommendation was to go with servers handling different set of subscribers and implementing a failover, per server.
Actually, I remember one spot where i read some of this data, at this link here:
http://www.voipuser.org/index.php?name=PNphpBB2&file=viewtopic&t=632...
Hope this helps you some.
Tracy
From: Jon Farmer jon@bctech.co.uk To: SER Mailing List serusers@iptel.org Subject: [Serusers] Scaling SER Date: Mon, 18 Sep 2006 20:28:13 +0100
Hi
I currently have a single SER server using MySQL for data storage. Due to the number of users I now have and to help redundancy I want to setup another SER server.
I have search the web and have not been able to find a tutorial on this so I hope someone on this list can help.
I need the SER servers to at least know about the location of clients registered with each server. Therefore can I point both servers at the same MySQL and for them to share the data?
Are there any issues around this strategy? Is there another way to accomplish what I want?
Regards
Jon
-- Jon Farmer Telford, Shropshire, UK _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
_________________________________________________________________ Get today's hot entertainment gossip http://movies.msn.com/movies/hotgossip
Hi again,
As a second note, implementing something like mediaproxy/proxydispatcher.py/mediaproxy.py and of course using the same, SER database you currently have, you can distribute load balancing and failover, per the INSTALL info found here for implementing mediaproxy:
http://mediaproxy.ag-projects.com/INSTALL
an excerpt states:
"Considering your domain is mydomain.com and you wan to dedicate 3 main servers and 2 fallbacks. The main servers you want to distribute traffic among are 2 1Ghz machines (named nat1 and nat2) and a 2Ghz machine (nat3). You want 25% from the traffic to go to each 1Ghz machine and 50% to the 2Ghz machine. For the fallbacks (nat4 and nat5) you want to distribute the traffic equally among the 2 machines....
_mediaproxy._tcp.mydomain.com. IN SRV 0 25 25060 nat1.mydomain.com. _mediaproxy._tcp.mydomain.com. IN SRV 0 25 25060 nat2.mydomain.com. _mediaproxy._tcp.mydomain.com. IN SRV 0 50 25060 nat3.mydomain.com. _mediaproxy._tcp.mydomain.com. IN SRV 10 50 25060 nat4.mydomain.com. _mediaproxy._tcp.mydomain.com. IN SRV 10 50 25060 nat5.mydomain.com. "
I hope this helps because it seems like it should work with no problem with many SER servers sharing the same db but balancing the load however you decide to distribute by manipulating/creating pertinent DNS SRV records. Actually, I do currently utilize mediaproxy and with regard to nat traversal/two-way audio capabilities, it serves me well.
Tracy
From: Jon Farmer jon@bctech.co.uk To: SER Mailing List serusers@iptel.org Subject: [Serusers] Scaling SER Date: Mon, 18 Sep 2006 20:28:13 +0100 " Hi
I currently have a single SER server using MySQL for data storage. Due to the number of users I now have and to help redundancy I want to setup another SER server.
I have search the web and have not been able to find a tutorial on this so I hope someone on this list can help.
I need the SER servers to at least know about the location of clients registered with each server. Therefore can I point both servers at the same MySQL and for them to share the data?
Are there any issues around this strategy? Is there another way to accomplish what I want?
Regards
Jon
-- Jon Farmer Telford, Shropshire, UK _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
_________________________________________________________________ Find a local pizza place, music store, museum and more then map the best route! http://local.live.com
-
Andrey Kuprianov -
Greger V. Teigre -
jh＠tutpro.com -
Jon Farmer -
Juha Heinanen
-
Natambu Obleton -
Tracy Lofton -
Vitaly Nikolaev