26 Mar
2008
26 Mar
'08
11:44 a.m.
Hi all,
In find some informations about an automatic end of call system.
The aim is to cut the call after 2 hours. So it's not specificly link to
a pre-paid system, but for all my ser user, I want to end the call after
2 hours.
Is there a existing solution to do that ? Or maybe some idea to deal
with this project ?
Thank you !
26 Mar
26 Mar
4:53 p.m.
inge wrote:
The aim is to cut the call after 2 hours. So it's not specificly link to
a pre-paid system, but for all my ser user, I want to end the call after
2 hours.
Is there a existing solution to do that ? Or maybe some idea to deal
with this project ?
If you are using accounting, you can use something like sipsak to
generate a BYE message from the information found in the accounting
data. Highly evil, but also highly effective.
Regards,
Martin
28 Mar
28 Mar
3:56 p.m.
Hi Martin,
Thanks for your answer.
I read informations about SIPSAK. But how can I generate a BYE only when
the communication duration is equal to 2 hours ?
Indeed, the RTP is establish between UAs in P2P. So, I would have to
test for each actives calls, everytime, the difference between start
date and current ?
Thanks for the support.
Le mercredi 26 mars 2008 à 16:53 +0100, Martin Hoffmann a écrit :
inge wrote:
The aim is to cut the call after 2 hours. So it's not specificly link to
a pre-paid system, but for all my ser user, I want to end the call after
2 hours.
Is there a existing solution to do that ? Or maybe some idea to deal
with this project ?
If you are using accounting, you can use something like sipsak to
generate a BYE message from the information found in the accounting
data. Highly evil, but also highly effective.
Regards,
Martin
6:13 p.m.
inge wrote:
I read informations about SIPSAK. But how can I generate a BYE only when
the communication duration is equal to 2 hours ?
I don't remember the details, but I think we were using a cron job do
generate CDRs from accounting data and on that occassion (where you have
to match INVITEs and BYEs, anyways), were generating those BYEs for
calls over a certain duration (ie., INVITEs a certain time ago).
Indeed, the RTP is establish between UAs in P2P. So, I
would have to
test for each actives calls, everytime, the difference between start
date and current ?
Pretty much, yes. Depending on the amount of calls you have and the
accuracy you need, you can vary the frequency of your cron job.
Regards,
Martin
7:27 p.m.
SO it's difficult to send a BYE after 2 hours exactly. Any other
solution maybe or more help on this workarround ?
Thanks
Le vendredi 28 mars 2008 à 18:13 +0100, Martin Hoffmann a écrit :
inge wrote:
I read informations about SIPSAK. But how can I generate a BYE only when
the communication duration is equal to 2 hours ?
I don't remember the details, but I think we were using a cron job do
generate CDRs from accounting data and on that occassion (where you have
to match INVITEs and BYEs, anyways), were generating those BYEs for
calls over a certain duration (ie., INVITEs a certain time ago).
Indeed, the RTP is establish between UAs in P2P.
So, I would have to
test for each actives calls, everytime, the difference between start
date and current ?
Pretty much, yes. Depending on the amount of calls you have and the
accuracy you need, you can vary the frequency of your cron job.
Regards,
Martin
9 Apr
9 Apr
11:33 p.m.
inge wrote:
SO it's difficult to send a BYE after 2 hours
exactly. Any other
solution maybe or more help on this workarround ?
You could probably build an app that, based on accounting information
keeps track of ongoing call and then BYEs them off after exactly two
hours.
Just keep in mind that this kind of thing actually is some sort of a man
in the middle attack and border line evil. If you want to do this
properly, you need a B2BUA.
Regards,
Martin
10 Apr
10 Apr
2:28 a.m.
Martin Hoffmann wrote:
inge wrote:
afaik for openser there is a 'bye2bye' on top of the dialog module,
that
sends BYE in both directions from the proxy.
SO it's difficult to send a BYE after 2 hours
exactly. Any other
solution maybe or more help on this workarround ?
You could probably build an app that, based on accounting information
keeps track of ongoing call and then BYEs them off after exactly two
hours.
Just keep in mind that this kind of thing actually is some sort of a man
in the middle attack and border line evil. If you want to do this
properly, you need a B2BUA.
you could use SEMS for that, i just added a call timer
application:
http://svn.berlios.de/wsvn/sems/trunk/doc/Readme.call_timer
it's easy, for a test run just do
svn co https://svn.berlios.de/svnroot/repos/sems/trunk sems_trunk
make -C sems_trunk/core
make -C sems_trunk/apps/call_timer
PREFIX=~/test_call_timer make -C sems_trunk/core install
PREFIX=~/test_call_timer make -C sems_trunk/apps/call_timer install
PREFIX=~/test_call_timer make -C sems_trunk/apps/call_timer install-cfg
and
~/test_call_timer/sbin/sems -f ~/test_call_timer/etc/sems/sems.conf -D 3 -E
and send your call to your_local_ip:5080
Stefan
Regards,
Martin
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Stefan Sayer
VoIP Services
stefan.sayer(a)iptego.com
www.iptego.com
iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
5:16 p.m.
Hi all,
Thanks for your answer. I don't use SEMS and OpenSER, so I think that
application will probably be the good workaround. Just need knwoledges
and documentations.
Wich languages could be pertinent to do that according to you ?
Thanks.
Le jeudi 10 avril 2008 à 02:28 +0200, Stefan Sayer a écrit :
Martin Hoffmann wrote:
inge wrote:
afaik for openser there is a 'bye2bye' on top of the dialog module,
that
sends BYE in both directions from the proxy.
SO it's difficult to send a BYE after 2 hours
exactly. Any other
solution maybe or more help on this workarround ?
You could probably build an app that, based on accounting information
keeps track of ongoing call and then BYEs them off after exactly two
hours.
Just keep in mind that this kind of thing actually is some sort of a man
in the middle attack and border line evil. If you want to do this
properly, you need a B2BUA.
you could use SEMS for that, i just added a call timer
application:
http://svn.berlios.de/wsvn/sems/trunk/doc/Readme.call_timer
it's easy, for a test run just do
svn co https://svn.berlios.de/svnroot/repos/sems/trunk sems_trunk
make -C sems_trunk/core
make -C sems_trunk/apps/call_timer
PREFIX=~/test_call_timer make -C sems_trunk/core install
PREFIX=~/test_call_timer make -C sems_trunk/apps/call_timer install
PREFIX=~/test_call_timer make -C sems_trunk/apps/call_timer install-cfg
and
~/test_call_timer/sbin/sems -f ~/test_call_timer/etc/sems/sems.conf -D 3 -E
and send your call to your_local_ip:5080
Stefan
Regards,
Martin
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
5867
days inactive
5882
days old
7 comments
3 participants
participants (3)
-
inge -
Martin Hoffmann -
Stefan Sayer