9 Jun
2008
9 Jun
'08
7:06 p.m.
Please let me know how can i configure this sip max session timer on the openser?
(SIP max timer) - If the openser doesn’t receive any BYE message from the origination
or termination equipment than the SIP max timer will forcefully kill the call by
generating the BYE on its own.
Thanks
Kchris
---------------------------------
Explore your hobbies and interests. Click here to begin.
9 Jun
9 Jun
7:21 p.m.
El Monday 09 June 2008 18:06:38 Kaeman Chris escribió:
Please let me know how can i configure this sip max
session timer on the
openser? (SIP max timer) - If the openser doesn’t receive any BYE message
from the origination or termination equipment than the SIP max timer will
forcefully kill the call by generating the BYE on its own.
OpenSer is not a call-statefull proxy, but a transaction stateful, so you
cannot rely on OpenSer to terminate a call after X seconds.
PD: Take a look at "dialog" module, but AFAIK it cannot terminate a call after
X seconds.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
10 Jun
10 Jun
1:28 a.m.
On Mon, Jun 9, 2008 at 12:21 PM, Iñaki Baz Castillo <ibc(a)in.ilimit.es> wrote:
El Monday 09 June 2008 18:06:38 Kaeman Chris
escribió:
A SIP proxy cannot send a BYE on its own (unless it's a 3GPP IMS SIP
proxy). With session-timers, proxies can clear their internal dialog
state if session refresh isn't performed by the UAs at the negotiated
interval.
--
Raj Jain
Please let me know how can i configure this sip
max session timer on the
openser? (SIP max timer) - If the openser doesn't receive any BYE message
from the origination or termination equipment than the SIP max timer will
forcefully kill the call by generating the BYE on its own.
OpenSer is not a call-statefull proxy, but a transaction stateful, so you
cannot rely on OpenSer to terminate a call after X seconds. 
11:18 a.m.
Hi Raj,
well, openser can send a BYE - dialog module keep the call state and is
able to send BYEs on both legs.
Regarding the Max Session Timer - take a look at SST module.
Regards,
Bogdan
Raj Jain wrote:
On Mon, Jun 9, 2008 at 12:21 PM, Iñaki Baz Castillo
<ibc(a)in.ilimit.es> wrote:
El Monday 09 June 2008 18:06:38 Kaeman Chris
escribió:
A SIP proxy cannot send a BYE on its own (unless it's a 3GPP IMS SIP
proxy). With session-timers, proxies can clear their internal dialog
state if session refresh isn't performed by the UAs at the negotiated
interval.
--
Raj Jain
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Please let me know how can i configure this sip
max session timer on the
openser? (SIP max timer) - If the openser doesn't receive any BYE message
from the origination or termination equipment than the SIP max timer will
forcefully kill the call by generating the BYE on its own.
OpenSer is not a call-statefull proxy, but a transaction stateful, so you
cannot rely on OpenSer to terminate a call after X seconds.
3:55 p.m.
Hi Bogdan,
Thanks. I wasn't aware of that. While sending a BYE from proxy on
session expiration makes some practical sense, RFC 4028 has a MUST NOT
clause on this (quote below). I'm not sure what problems this can
cause. Perhaps, this behavior can be made configurable (i.e. by
default OpenSER will clear its internal state only, but if this flag
was set, it'll send a BYE as well).
8.3. Session Expiration
When the current time equals or passes the session expiration for a
session, the proxy MAY remove associated call state, and MAY free any
resources associated with the call. Unlike the UA, it MUST NOT send
a BYE.
--
Raj Jain
On Tue, Jun 10, 2008 at 4:18 AM, Bogdan-Andrei Iancu
<bogdan(a)voice-system.ro> wrote:
Hi Raj,
well, openser can send a BYE - dialog module keep the call state and is able
to send BYEs on both legs.
Regarding the Max Session Timer - take a look at SST module.
Regards,
Bogdan
Raj Jain wrote:
On Mon, Jun 9, 2008 at 12:21 PM, Iñaki Baz Castillo <ibc(a)in.ilimit.es>
wrote:
El Monday 09 June 2008 18:06:38 Kaeman Chris escribió:
A SIP proxy cannot send a BYE on its own (unless it's a 3GPP IMS SIP
proxy). With session-timers, proxies can clear their internal dialog
state if session refresh isn't performed by the UAs at the negotiated
interval.
--
Raj Jain
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Please let me know how can i configure this sip max session timer on
the
openser? (SIP max timer) - If the openser doesn't receive any BYE
message
from the origination or termination equipment than the SIP max timer
will
forcefully kill the call by generating the BYE on its own.
OpenSer is not a call-statefull proxy, but a transaction stateful, so you
cannot rely on OpenSer to terminate a call after X seconds.
4:09 p.m.
El Tuesday 10 June 2008 14:55:42 Raj Jain escribió:
Hi Bogdan,
Thanks. I wasn't aware of that. While sending a BYE from proxy on
session expiration makes some practical sense, RFC 4028 has a MUST NOT
clause on this (quote below). I'm not sure what problems this can
cause. Perhaps, this behavior can be made configurable (i.e. by
default OpenSER will clear its internal state only, but if this flag
was set, it'll send a BYE as well).
In fact, when OpenSer is working with "dialog" module it becomes a "call
stateful" proxy, so maybe in this scenario is it valid to send a BYE?
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
4:24 p.m.
On Tue, Jun 10, 2008 at 9:09 AM, Iñaki Baz Castillo <ibc(a)in.ilimit.es> wrote:
In fact, when OpenSer is working with
"dialog" module it becomes a "call
stateful" proxy, so maybe in this scenario is it valid to send a BYE?
Well, it is not valid in the IETF's version of SIP (look at the proxy
behavior in RFC 3261 and the MUST NOT clause in RFC 4028). But, still
it makes some practical sense to do this, that's why I proposed that
it should be made configurable.
--
Raj Jain
6015
days inactive
6016
days old
6 comments
4 participants
participants (4)
-
Bogdan-Andrei Iancu -
Iñaki Baz Castillo -
Kaeman Chris -
Raj Jain