5 Apr
2005
5 Apr
'05
10:07 p.m.
So I can get replication working, but I constantly am getting errors
about receiving SERs usrloc not being able to insert into the
database. My guess is because the contact is already there by the
originating SER. I have a MySQL cluster that both SERs are using. My
question is this, how can I save the contact in the SER that is
receiving the contact, without SER trying to write the contact to the
DB?
6 Apr
6 Apr
8:55 a.m.
You have a cluster and you want to do replication in SER? Do your SER
servers have one or several databases in mysql? You cannot do both
replication and have one DB. The problem of using a cluster is that SER
will write back everything to the database, but there is no "refresh" when
looking up a location, so you cannot be sure that SER B will pick up what
SER A stored.
g-)
AJ Grinnell wrote:
So I can get replication working, but I constantly am
getting errors
about receiving SERs usrloc not being able to insert into the
database. My guess is because the contact is already there by the
originating SER. I have a MySQL cluster that both SERs are using. My
question is this, how can I save the contact in the SER that is
receiving the contact, without SER trying to write the contact to the
DB?
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
4:05 p.m.
Has anyone ever seen the save_memory() function in the registrar module?
I'm wondering exactly what this does. Assuming I have two (2) SER servers
connected to the __same__ MySQL server, it seems like something like this
should be legal:
listen=10.255.15.1 <http://10.255.15.1>
modparam("usrloc", "db_mode", 2)
route {
if (method=="REGISTER") {
if (src_ip==10.255.15.1 <http://10.255.15.1>) { # ip of peer SER proxy
save_memory();
} else {
save("location");
t_replicate("10.255.15.2 <http://10.255.15.2>", 5060);
};
};
}
What I don't know, however, is will 10.255.15.2 <http://10.255.15.2> attempt
to write to the location table.
Does anyone know about this?
Regards,
Paul
On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
You have a cluster and you want to do replication in SER? Do your SER
servers have one or several databases in mysql? You cannot do both
replication and have one DB. The problem of using a cluster is that SER
will write back everything to the database, but there is no "refresh" when
looking up a location, so you cannot be sure that SER B will pick up what
SER A stored.
g-)
AJ Grinnell wrote:
So I can get replication working, but I
constantly am getting errors
about receiving SERs usrloc not being able to insert into the
database. My guess is because the contact is already there by the
originating SER. I have a MySQL cluster that both SERs are using. My
question is this, how can I save the contact in the SER that is
receiving the contact, without SER trying to write the contact to the
DB?
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
4:28 p.m.
That is exactly what I would need.
On Apr 6, 2005 9:05 AM, Java Rockx <javarockx(a)gmail.com> wrote:
Has anyone ever seen the save_memory() function in the
registrar module?
I'm wondering exactly what this does. Assuming I have two (2) SER servers
connected to the __same__ MySQL server, it seems like something like this
should be legal:
listen=10.255.15.1
modparam("usrloc", "db_mode", 2)
route {
if (method=="REGISTER") {
if (src_ip==10.255.15.1) { # ip of peer SER proxy
save_memory();
} else {
save("location");
t_replicate("10.255.15.2", 5060);
};
};
}
What I don't know, however, is will 10.255.15.2 attempt to write to the
location table.
Does anyone know about this?
Regards,
Paul
On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
You have a cluster and you want to do replication in SER? Do your SER
servers have one or several databases in mysql? You cannot do both
replication and have one DB. The problem of using a cluster is that SER
will write back everything to the database, but there is no "refresh" when
looking up a location, so you cannot be sure that SER B will pick up what
SER A stored.
g-)
AJ Grinnell wrote:
So I can get replication working, but I
constantly am getting errors
about receiving SERs usrloc not being able to insert into the
database. My guess is because the contact is already there by the
originating SER. I have a MySQL cluster that both SERs are using. My
question is this, how can I save the contact in the SER that is
receiving the contact, without SER trying to write the contact to the
DB?
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
4:48 p.m.
I just tested the save_memory() function and it works as I suspected.
The only bug in my example is that save_memory() should be
save_memory("location")
Regards,
Paul
On Apr 6, 2005 9:28 AM, AJ Grinnell <ajgrinnell(a)gmail.com> wrote:
That is exactly what I would need.
On Apr 6, 2005 9:05 AM, Java Rockx <javarockx(a)gmail.com> wrote:
Has anyone ever seen the save_memory() function
in the registrar module?
I'm wondering exactly what this does. Assuming I have two (2) SER
servers
connected to the __same__ MySQL server, it seems
like something like
this
should be legal:
listen=10.255.15.1 <http://10.255.15.1>
modparam("usrloc", "db_mode", 2)
route {
if (method=="REGISTER") {
if (src_ip==10.255.15.1 <http://10.255.15.1>) { # ip of peer SER proxy
save_memory();
} else {
save("location");
t_replicate("10.255.15.2 <http://10.255.15.2>", 5060);
};
};
}
What I don't know, however, is will 10.255.15.2 <http://10.255.15.2>attempt to
write to the
location table.
Does anyone know about this?
Regards,
Paul
On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
>
> You have a cluster and you want to do replication in SER? Do your SER
> servers have one or several databases in mysql? You cannot do both
> replication and have one DB. The problem of using a cluster is that
SER
> will write back everything to the database,
but there is no "refresh"
when
> looking up a location, so you cannot be sure
that SER B will pick up
what
> SER A stored.
> g-)
>
> AJ Grinnell wrote:
> > So I can get replication working, but I constantly am getting errors
> > about receiving SERs usrloc not being able to insert into the
> > database. My guess is because the contact is already there by the
> > originating SER. I have a MySQL cluster that both SERs are using. My
> > question is this, how can I save the contact in the SER that is
> > receiving the contact, without SER trying to write the contact to
the
DB?
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
7 Apr
7 Apr
8:26 a.m.
So, just to be sure that I understand it's use correctly:
It will save the UA's location to memory, but not to DB, and it will reply to UA as
save() does?
g-)
---- Original Message ----
From: Java Rockx
To: AJ Grinnell
Cc: Greger V. Teigre ; serusers(a)lists.iptel.org
Sent: Wednesday, April 06, 2005 03:48 PM
Subject: Re: [Serusers] More usrloc sync questions
I just tested the save_memory() function and it works
as I suspected.
The only bug in my example is that save_memory() should be
save_memory("location")
Regards,
Paul
On Apr 6, 2005 9:28 AM, AJ Grinnell <ajgrinnell(a)gmail.com> wrote:
That is exactly what I would need.
On Apr 6, 2005 9:05 AM, Java Rockx <javarockx(a)gmail.com> wrote:
> Has anyone ever seen the save_memory() function in the registrar
> module?
>
> I'm wondering exactly what this does. Assuming I have two (2) SER
> servers connected to the __same__ MySQL server, it seems like
> something like this should be legal:
>
> listen=10.255.15.1
> modparam("usrloc", "db_mode", 2)
>
> route {
>
> if (method=="REGISTER") {
>
> if (src_ip==10.255.15.1) { # ip of peer SER proxy
>
> save_memory();
>
> } else {
>
> save("location");
> t_replicate("10.255.15.2", 5060);
>
> };
> };
> }
>
>
> What I don't know, however, is will 10.255.15.2 attempt to write to
> the location table.
>
> Does anyone know about this?
>
> Regards,
> Paul
>
>
>
>
> On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
>>
>> You have a cluster and you want to do replication in SER? Do your
>> SER servers have one or several databases in mysql? You cannot do
>> both replication and have one DB. The problem of using a cluster
>> is that SER will write back everything to the database, but there
>> is no "refresh" when looking up a location, so you cannot be sure
>> that SER B will pick up what SER A stored.
>> g-)
>>
>> AJ Grinnell wrote:
>>> So I can get replication working, but I constantly am getting
>>> errors about receiving SERs usrloc not being able to insert into
>>> the database. My guess is because the contact is already there by
>>> the originating SER. I have a MySQL cluster that both SERs are
>>> using. My question is this, how can I save the contact in the SER
>>> that is receiving the contact, without SER trying to write the
>>> contact to the DB?
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> serusers(a)lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers(a)lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
2:34 p.m.
That appears to be what it does. I would love for the registrar module
README to include documentation of this function to be certain of its
purpose.
P
On Apr 7, 2005 1:26 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
So, just to be sure that I understand it's use correctly:
It will save the UA's location to memory, but not to DB, and it will reply
to UA as save() does?
g-)
---- Original Message ----
From: Java Rockx
To: AJ Grinnell
Cc: Greger V. Teigre ; serusers(a)lists.iptel.org
Sent: Wednesday, April 06, 2005 03:48 PM
Subject: Re: [Serusers] More usrloc sync questions
I just tested the save_memory() function and it
works as I suspected.
The only bug in my example is that save_memory() should be
save_memory("location")
Regards,
Paul
On Apr 6, 2005 9:28 AM, AJ Grinnell <ajgrinnell(a)gmail.com> wrote:
That is exactly what I would need.
On Apr 6, 2005 9:05 AM, Java Rockx <javarockx(a)gmail.com> wrote:
> Has anyone ever seen the save_memory() function in the registrar
> module?
>
> I'm wondering exactly what this does. Assuming I have two (2) SER
> servers connected to the __same__ MySQL server, it seems like
> something like this should be legal:
>
> listen=10.255.15.1 <http://10.255.15.1>
> modparam("usrloc", "db_mode", 2)
>
> route {
>
> if (method=="REGISTER") {
>
> if (src_ip==10.255.15.1 <http://10.255.15.1>) { # ip of peer SER proxy
>
> save_memory();
>
> } else {
>
> save("location");
> t_replicate("10.255.15.2 <http://10.255.15.2>", 5060);
>
> };
> };
> }
>
>
> What I don't know, however, is will 10.255.15.2 <http://10.255.15.2>attempt
to write to
> the location table.
>
> Does anyone know about this?
>
> Regards,
> Paul
>
>
>
>
> On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
>>
>> You have a cluster and you want to do replication in SER? Do your
>> SER servers have one or several databases in mysql? You cannot do
>> both replication and have one DB. The problem of using a cluster
>> is that SER will write back everything to the database, but there
>> is no "refresh" when looking up a location, so you cannot be sure
>> that SER B will pick up what SER A stored.
>> g-)
>>
>> AJ Grinnell wrote:
>>> So I can get replication working, but I constantly am getting
>>> errors about receiving SERs usrloc not being able to insert into
>>> the database. My guess is because the contact is already there by
>>> the originating SER. I have a MySQL cluster that both SERs are
>>> using. My question is this, how can I save the contact in the SER
>>> that is receiving the contact, without SER trying to write the
>>> contact to the DB?
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> serusers(a)lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers(a)lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
9 Apr
9 Apr
11:40 a.m.
Yes, this is exactly what the function does.
Jan.
On 07-04 07:34, Java Rockx wrote:
That appears to be what it does. I would love for the
registrar module
README to include documentation of this function to be certain of its
purpose.
P
On Apr 7, 2005 1:26 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
>
> So, just to be sure that I understand it's use correctly:
> It will save the UA's location to memory, but not to DB, and it will reply
> to UA as save() does?
> g-)
> ---- Original Message ----
> From: Java Rockx
> To: AJ Grinnell
> Cc: Greger V. Teigre ; serusers(a)lists.iptel.org
> Sent: Wednesday, April 06, 2005 03:48 PM
> Subject: Re: [Serusers] More usrloc sync questions
>
> > I just tested the save_memory() function and it works as I suspected.
> >
> > The only bug in my example is that save_memory() should be
> > save_memory("location")
> >
> > Regards,
> > Paul
> >
> >
> > On Apr 6, 2005 9:28 AM, AJ Grinnell <ajgrinnell(a)gmail.com> wrote:
> > That is exactly what I would need.
> >
> > On Apr 6, 2005 9:05 AM, Java Rockx <javarockx(a)gmail.com> wrote:
> >> Has anyone ever seen the save_memory() function in the registrar
> >> module?
> >>
> >> I'm wondering exactly what this does. Assuming I have two (2) SER
> >> servers connected to the __same__ MySQL server, it seems like
> >> something like this should be legal:
> >>
> >> listen=10.255.15.1 <http://10.255.15.1>
> >> modparam("usrloc", "db_mode", 2)
> >>
> >> route {
> >>
> >> if (method=="REGISTER") {
> >>
> >> if (src_ip==10.255.15.1 <http://10.255.15.1>) { # ip of peer SER
proxy
> >>
> >> save_memory();
> >>
> >> } else {
> >>
> >> save("location");
> >> t_replicate("10.255.15.2 <http://10.255.15.2>", 5060);
> >>
> >> };
> >> };
> >> }
> >>
> >>
> >> What I don't know, however, is will 10.255.15.2
<http://10.255.15.2>attempt to write to
> >> the location table.
> >>
> >> Does anyone know about this?
> >>
> >> Regards,
> >> Paul
> >>
> >>
> >>
> >>
> >> On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
> >>>
> >>> You have a cluster and you want to do replication in SER? Do your
> >>> SER servers have one or several databases in mysql? You cannot do
> >>> both replication and have one DB. The problem of using a cluster
> >>> is that SER will write back everything to the database, but there
> >>> is no "refresh" when looking up a location, so you cannot be
sure
> >>> that SER B will pick up what SER A stored.
> >>> g-)
> >>>
> >>> AJ Grinnell wrote:
> >>>> So I can get replication working, but I constantly am getting
> >>>> errors about receiving SERs usrloc not being able to insert into
> >>>> the database. My guess is because the contact is already there by
> >>>> the originating SER. I have a MySQL cluster that both SERs are
> >>>> using. My question is this, how can I save the contact in the SER
> >>>> that is receiving the contact, without SER trying to write the
> >>>> contact to the DB?
> >>>>
> >>>> _______________________________________________
> >>>> Serusers mailing list
> >>>> serusers(a)lists.iptel.org
> >>>> http://lists.iptel.org/mailman/listinfo/serusers
> >>>
> >>> _______________________________________________
> >>> Serusers mailing list
> >>> serusers(a)lists.iptel.org
> >>> http://lists.iptel.org/mailman/listinfo/serusers
>
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
11:40 a.m.
save_memory updates the memory cache only, it will not write anything
into the database. Originally it was written to avoid db update
conflicts when mysql replication is being used.
Jan.
On 06-04 09:05, Java Rockx wrote:
Has anyone ever seen the save_memory() function in the
registrar module?
I'm wondering exactly what this does. Assuming I have two (2) SER servers
connected to the __same__ MySQL server, it seems like something like this
should be legal:
listen=10.255.15.1 <http://10.255.15.1>
modparam("usrloc", "db_mode", 2)
route {
if (method=="REGISTER") {
if (src_ip==10.255.15.1 <http://10.255.15.1>) { # ip of peer SER proxy
save_memory();
} else {
save("location");
t_replicate("10.255.15.2 <http://10.255.15.2>", 5060);
};
};
}
What I don't know, however, is will 10.255.15.2 <http://10.255.15.2> attempt
to write to the location table.
Does anyone know about this?
Regards,
Paul
On Apr 6, 2005 1:55 AM, Greger V. Teigre <greger(a)teigre.com> wrote:
>
> You have a cluster and you want to do replication in SER? Do your SER
> servers have one or several databases in mysql? You cannot do both
> replication and have one DB. The problem of using a cluster is that SER
> will write back everything to the database, but there is no "refresh"
when
> looking up a location, so you cannot be sure that SER B will pick up what
> SER A stored.
> g-)
>
> AJ Grinnell wrote:
> > So I can get replication working, but I constantly am getting errors
> > about receiving SERs usrloc not being able to insert into the
> > database. My guess is because the contact is already there by the
> > originating SER. I have a MySQL cluster that both SERs are using. My
> > question is this, how can I save the contact in the SER that is
> > receiving the contact, without SER trying to write the contact to the
> > DB?
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers(a)lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
7167
days inactive
7171
days old
8 comments
4 participants
participants (4)
-
AJ Grinnell -
Greger V. Teigre -
Jan Janak -
Java Rockx