27 Jan
2006
27 Jan
'06
11:49 a.m.
Hello members,
I have SER and SEMS on the same machine and it works fine. For
performance reasons, I would like to them to be on separate machines.
My query is the fact that SEMS uses the email address from the
subscriber table in SER db. Do I need to have SER db on the machine
where SEMS is running (means 2 identical dbs) or how can I achieve this?
Regards,
Amos.
27 Jan
27 Jan
noon
I think SER and SEMS must be on the same machine becasue they use FIFO
or UNIX socket to interact.
Sam.
2006/1/27, Amos M. Nungu <amos.nungu(a)gmail.com>om>:
Hello members,
I have SER and SEMS on the same machine and it works fine. For
performance reasons, I would like to them to be on separate machines.
My query is the fact that SEMS uses the email address from the
subscriber table in SER db. Do I need to have SER db on the machine
where SEMS is running (means 2 identical dbs) or how can I achieve this?
Regards,
Amos.
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
12:58 p.m.
SER and SEMS of SOME sort must be on the same machine, but it doesn't have to
be your main SER. I have a copy of SER running on a separate machine with SEMS
that is pared down considerable and does nothing but handle SEMS stuff... the
main SER server forwards calls onto the SER/SEMS server (on a different
machine) for the sake of performance.
You DO have to have a copy of at least the subscriber table (or, really, only
PARTS of the subscriber table) for the voicemail app to work as it grabs the
email address.
Your choices are to either have a DB url that points to the original DB or
replicate your subscriber info to two different tables.
We chose the latter. On creation of a user account, we have a trigger that
replicates the subscriber info to a separate DB on the SER/SEMS machine.
During testing, however, we had it originally set up to just point to the
original DB and noticed no real performance hit.
N.
On Fri, 27 Jan 2006 12:00:08 +0100, samuel wrote
I think SER and SEMS must be on the same machine
becasue they use
FIFO or UNIX socket to interact.
Sam.
2006/1/27, Amos M. Nungu <amos.nungu(a)gmail.com>om>:
Hello members,
I have SER and SEMS on the same machine and it works fine. For
performance reasons, I would like to them to be on separate machines.
My query is the fact that SEMS uses the email address from the
subscriber table in SER db. Do I need to have SER db on the machine
where SEMS is running (means 2 identical dbs) or how can I achieve this?
Regards,
Amos.
_______________________________________________
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 
1:04 p.m.
you may also try to put the email address in the forwarded request at proxy
and restore it from there at SER/SEMS box. This saves a DB lookup. -jiri
At 12:58 PM 1/27/2006, sip wrote:
SER and SEMS of SOME sort must be on the same machine,
but it doesn't have to
be your main SER. I have a copy of SER running on a separate machine with SEMS
that is pared down considerable and does nothing but handle SEMS stuff... the
main SER server forwards calls onto the SER/SEMS server (on a different
machine) for the sake of performance.
You DO have to have a copy of at least the subscriber table (or, really, only
PARTS of the subscriber table) for the voicemail app to work as it grabs the
email address.
Your choices are to either have a DB url that points to the original DB or
replicate your subscriber info to two different tables.
We chose the latter. On creation of a user account, we have a trigger that
replicates the subscriber info to a separate DB on the SER/SEMS machine.
During testing, however, we had it originally set up to just point to the
original DB and noticed no real performance hit.
N.
On Fri, 27 Jan 2006 12:00:08 +0100, samuel wrote
--
Jiri Kuthan http://iptel.org/~jiri/
I think SER and SEMS must be on the same machine
becasue they use
FIFO or UNIX socket to interact.
Sam.
2006/1/27, Amos M. Nungu <amos.nungu(a)gmail.com>om>:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hello members,
I have SER and SEMS on the same machine and it works fine. For
performance reasons, I would like to them to be on separate machines.
My query is the fact that SEMS uses the email address from the
subscriber table in SER db. Do I need to have SER db on the machine
where SEMS is running (means 2 identical dbs) or how can I achieve this?
Regards,
Amos.
_______________________________________________
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 Feb
2 Feb
2:28 p.m.
Jiri,
I didn't get it cleary what you mean. I would like to try it if you can
explain a bit more.
NB.
Thanks for everyone. I used the method advised by "sip" and works
perfect (SER 0.9.3, SEMS 0.9.0).
Regards.
Jiri Kuthan wrote:
you may also try to put the email address in the
forwarded request at proxy and restore it from there at SER/SEMS box. This saves a DB
lookup. -jiri
At 12:58 PM 1/27/2006, sip wrote:
SER and SEMS of SOME sort must be on the same
machine, but it doesn't have to
be your main SER. I have a copy of SER running on a separate machine with SEMS
that is pared down considerable and does nothing but handle SEMS stuff... the
main SER server forwards calls onto the SER/SEMS server (on a different
machine) for the sake of performance.
You DO have to have a copy of at least the subscriber table (or, really, only
PARTS of the subscriber table) for the voicemail app to work as it grabs the
email address.
Your choices are to either have a DB url that points to the original DB or
replicate your subscriber info to two different tables.
We chose the latter. On creation of a user account, we have a trigger that
replicates the subscriber info to a separate DB on the SER/SEMS machine.
During testing, however, we had it originally set up to just point to the
original DB and noticed no real performance hit.
N.
On Fri, 27 Jan 2006 12:00:08 +0100, samuel wrote
--
Jiri Kuthan http://iptel.org/~jiri/
I think SER and SEMS must be on the same machine
becasue they use
FIFO or UNIX socket to interact.
Sam.
2006/1/27, Amos M. Nungu <amos.nungu(a)gmail.com>om>:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hello members,
I have SER and SEMS on the same machine and it works fine. For
performance reasons, I would like to them to be on separate machines.
My query is the fact that SEMS uses the email address from the
subscriber table in SER db. Do I need to have SER db on the machine
where SEMS is running (means 2 identical dbs) or how can I achieve this?
Regards,
Amos.
_______________________________________________
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
3:55 p.m.
New subject: [Sems] Re: [Serusers] SER & SEMS on separate machines
Hi,
IMO, what Jiri wanted to say is that, when you get a an INVITE that is
supposed to be redirected to SEMS, you should add the e-mail address to the
Invite SIP message, so that the SEMS machine does not need to search for the
e-mail address in another machine.
Jose Simoes
On 2/2/06, Amos Nungu <amos.nungu(a)gmail.com> wrote:
Jiri,
I didn't get it cleary what you mean. I would like to try it if you can
explain a bit more.
NB.
Thanks for everyone. I used the method advised by "sip" and works
perfect (SER 0.9.3, SEMS 0.9.0).
Regards.
Jiri Kuthan wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Sems mailing list
sems(a)lists.iptel.org
http://lists.iptel.org/cgi-bin/mailman/listinfo/sems
you may also try to put the email address in the
forwarded request at
proxy and restore it from there at SER/SEMS box. This saves a
DB lookup.
-jiri
At 12:58 PM 1/27/2006, sip wrote:
>SER and SEMS of SOME sort must be on the same machine, but it doesn't
have
to
>be your main SER. I have a copy of SER running
on a separate machine
with SEMS
>that is pared down considerable and does
nothing but handle SEMS
stuff... the
>main SER server forwards calls onto the
SER/SEMS server (on a different
>machine) for the sake of performance.
>
>You DO have to have a copy of at least the subscriber table (or, really,
only
>PARTS of the subscriber table) for the
voicemail app to work as it grabs
the
>email address.
>
>Your choices are to either have a DB url that points to the original DB
or
>replicate your subscriber info to two
different tables.
>
>We chose the latter. On creation of a user account, we have a trigger
that
>replicates the subscriber info to a separate
DB on the SER/SEMS machine.
>During testing, however, we had it originally set up to just point to
the
>original DB and noticed no real performance
hit.
>
>N.
>
>On Fri, 27 Jan 2006 12:00:08 +0100, samuel wrote
>
>
>>I think SER and SEMS must be on the same machine becasue they use
>>FIFO or UNIX socket to interact.
>>
>>Sam.
>>2006/1/27, Amos M. Nungu <amos.nungu(a)gmail.com>om>:
>>
>>
>>>Hello members,
>>>
>>>I have SER and SEMS on the same machine and it works fine. For
>>>performance reasons, I would like to them to be on separate machines.
>>>
>>>My query is the fact that SEMS uses the email address from the
>>>subscriber table in SER db. Do I need to have SER db on the machine
>>>where SEMS is running (means 2 identical dbs) or how can I achieve
this?
>
>Regards,
>Amos.
>
>_______________________________________________
>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
6683
days inactive
6689
days old
5 comments
6 participants
participants (6)
-
Amos M. Nungu -
Amos Nungu
-
Jiri Kuthan -
samuel -
sip -
Voipers Portugal