31 Oct
2006
31 Oct
'06
4:46 p.m.
Hi list,
I am trying to realise dynamic invite-timeout-timers loading timer-settings
per call from my database using avp. It seems to work perfectly on my
development-system but fails nearly completly in my high loaded
life-environment. According to my logs, timer values are set correctly (eg.:
reply_received: FR_INV_TIMER = 15, see modules/tm/t_reply.c:1371), but most
of the times the timers have no effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are not
written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding this
issue. I Also failed accessing the bug-tracker (http://bugs.sip-router.org/),
it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a workaround?
Best regards,
Marcus Hunger
6 Nov
6 Nov
6:40 a.m.
Hello Marcus.
On Tuesday 31 October 2006 15:46, Marcus Hunger wrote:
Hi list,
I am trying to realise dynamic invite-timeout-timers loading timer-settings
per call from my database using avp. It seems to work perfectly on my
development-system but fails nearly completly in my high loaded
life-environment. According to my logs, timer values are set correctly
(eg.: reply_received: FR_INV_TIMER = 15, see modules/tm/t_reply.c:1371),
but most of the times the timers have no effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are not
written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding
this issue. I Also failed accessing the bug-tracker
(http://bugs.sip-router.org/), it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a workaround?
I'm not sure but the new timer implementation in SER head might solve this
problem.
Nils
11:17 a.m.
At 05:40 06/11/2006, Nils Ohlmeier wrote:
Hello Marcus.
On Tuesday 31 October 2006 15:46, Marcus Hunger wrote:
I would definitely try this first. The thing is that the old timer system
was fast but not flexible, and variable timers just slowed down. The new
timer system should address that. Can you share with us if it made things
better for you?
-jiri
--
Jiri Kuthan http://iptel.org/~jiri/
Hi list,
I am trying to realise dynamic invite-timeout-timers loading timer-settings
per call from my database using avp. It seems to work perfectly on my
development-system but fails nearly completly in my high loaded
life-environment. According to my logs, timer values are set correctly
(eg.: reply_received: FR_INV_TIMER = 15, see modules/tm/t_reply.c:1371),
but most of the times the timers have no effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are not
written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding
this issue. I Also failed accessing the bug-tracker
(http://bugs.sip-router.org/), it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a workaround?
I'm not sure but the new timer implementation in SER head might solve this
problem.
3:17 p.m.
Hi Jiri,
are you aware of a backport of the new timers from 0.10
to 0.9.6? Though we are going to test the prerelease, it is marked as
unstable, so it's hardly an option for us. Any help on this issue would be
great.
Marcus
On Monday 06 November 2006 10:17, Jiri Kuthan wrote:
At 05:40 06/11/2006, Nils Ohlmeier wrote:
Hello Marcus.
On Tuesday 31 October 2006 15:46, Marcus Hunger wrote:
I would definitely try this first. The thing is that the old timer system
was fast but not flexible, and variable timers just slowed down. The new
timer system should address that. Can you share with us if it made things
better for you?
-jiri
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hi list,
I am trying to realise dynamic invite-timeout-timers loading
timer-settings per call from my database using avp. It seems to work
perfectly on my development-system but fails nearly completly in my high
loaded life-environment. According to my logs, timer values are set
correctly (eg.: reply_received: FR_INV_TIMER = 15, see
modules/tm/t_reply.c:1371), but most of the times the timers have no
effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are
not written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding
this issue. I Also failed accessing the bug-tracker
(http://bugs.sip-router.org/), it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a
workaround?
I'm not sure but the new timer implementation in SER head might solve this
problem.
5:26 p.m.
Hi Marcus,
I think we are now at the stage that the testing effort for Ottendorf is
more profittable than backporting effort. I understand that this is not
the answer you were hopeful to hear, but in the end of the day it is
about migration versus backporting evil and it seems that the latter
is more laborous for you.
-Jiri
At 14:17 06/11/2006, Marcus Hunger wrote:
Hi Jiri,
are you aware of a backport of the new timers from 0.10
to 0.9.6? Though we are going to test the prerelease, it is marked as
unstable, so it's hardly an option for us. Any help on this issue would be
great.
Marcus
On Monday 06 November 2006 10:17, Jiri Kuthan wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
At 05:40 06/11/2006, Nils Ohlmeier wrote:
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hello Marcus.
On Tuesday 31 October 2006 15:46, Marcus Hunger wrote:
I would definitely try this first. The thing is that the old timer system
was fast but not flexible, and variable timers just slowed down. The new
timer system should address that. Can you share with us if it made things
better for you?
-jiri
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hi list,
I am trying to realise dynamic invite-timeout-timers loading
timer-settings per call from my database using avp. It seems to work
perfectly on my development-system but fails nearly completly in my high
loaded life-environment. According to my logs, timer values are set
correctly (eg.: reply_received: FR_INV_TIMER = 15, see
modules/tm/t_reply.c:1371), but most of the times the timers have no
effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are
not written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding
this issue. I Also failed accessing the bug-tracker
(http://bugs.sip-router.org/), it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a
workaround?
I'm not sure but the new timer implementation in SER head might solve this
problem. 
10 Nov
10 Nov
3:17 p.m.
AFAI understand, you might also consider that fr_inv_timer only fires if
at least one reply to the INVITE is received. If this "high loaded
life-environment" might be reached through a narrow pipe, or drops
packets, the transaction will expire after fr_timer, only.
Of course, you could try the release to come and see if find improvements.
Hth,
Bogdan.
Marcus Hunger wrote:
Hi list,
I am trying to realise dynamic invite-timeout-timers loading timer-settings
per call from my database using avp. It seems to work perfectly on my
development-system but fails nearly completly in my high loaded
life-environment. According to my logs, timer values are set correctly (eg.:
reply_received: FR_INV_TIMER = 15, see modules/tm/t_reply.c:1371), but most
of the times the timers have no effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are not
written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding this
issue. I Also failed accessing the bug-tracker (http://bugs.sip-router.org/),
it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a workaround?
Best regards,
Marcus Hunger
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Bogdan Pintea
iptego GmbH - VoIP Security
http://www.iptego.de
7:50 p.m.
I don't want to begin to be tiresome, but I think you should try Ottendorf.
The pre-ottendorf-ical timer system had its shortcomings, which bubble up
to the surface in loaded environments like yours.
-jiri
At 14:17 10/11/2006, Bogdan Pintea wrote:
AFAI understand, you might also consider that
fr_inv_timer only fires if
at least one reply to the INVITE is received. If this "high loaded
life-environment" might be reached through a narrow pipe, or drops
packets, the transaction will expire after fr_timer, only.
Of course, you could try the release to come and see if find improvements.
Hth,
Bogdan.
Marcus Hunger wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
Hi list,
I am trying to realise dynamic invite-timeout-timers loading timer-settings
per call from my database using avp. It seems to work perfectly on my
development-system but fails nearly completly in my high loaded
life-environment. According to my logs, timer values are set correctly (eg.:
reply_received: FR_INV_TIMER = 15, see modules/tm/t_reply.c:1371), but most
of the times the timers have no effect.
My setup is similar to
http://siprouter.onsip.org/doc/gettingstarted/ch09.html, but avps are not
written by hand, but acquired with:
modparam("tm", "fr_inv_timer_avp", "mytimer");
avp_db_load("$ruri/username","s:mytimer");
'mytimer' is an attribute in an usr_preferences-table.
Ser's version is 0.9.6.
I already searched the list-archives without finding anything regarding this
issue. I Also failed accessing the bug-tracker (http://bugs.sip-router.org/),
it gave me an internal server error.
Has anybody experienced this effect? Is this a bug? Is there a workaround?
Best regards,
Marcus Hunger
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Bogdan Pintea
iptego GmbH - VoIP Security
http://www.iptego.de
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6587
days inactive
6597
days old
6 comments
4 participants
participants (4)
-
Bogdan Pintea -
Jiri Kuthan -
Marcus Hunger -
Nils Ohlmeier