1 Aug
2006
1 Aug
'06
1:26 p.m.
Hi!
As far as I know, SER does not have functionality of limiting
number of calls on per-user basis. It was discussed years ago,
and the reason for that was "We don't have ability to know is call
still alive"
(http://lists.iptel.org/pipermail/serusers/2004-November/013035.html)
But, in April 2005, RFC 4028 (Session Timers in SIP) appeared, and
it (at least theoretically) can be utilised to achieve knowlege of active
dialogs, and, as result - on number of active calls.
And this RFC looks like supported on Cisco gateways:
U X.X.X.X:59104 -> X.X.X.X:5060
INVITE sip:aaaaaaa@X.X.X.X:5060 SIP/2.0.
Supported: 100rel,timer,replaces.
^^^^^
Min-SE: 1800.
^^^^^^^^^^^^^^
User-Agent: Cisco-SIPGateway/IOS-12.x.
Question: is this RFC/functionality planned to be supported in SER ?
If not - are there any good intro on "How to write SER module by yourself" ? :)
6 Aug
6 Aug
1:21 p.m.
You can write a ser script to implement session timer, we have indeed done that.
That still does not give you access to call state. You would have to write
own module which keeps it and hope that session timer will provide needed reliability
(which may not be always the case).
-jiri
At 12:26 01/08/2006, Alexandre Snarskii wrote:
Hi!
As far as I know, SER does not have functionality of limiting
number of calls on per-user basis. It was discussed years ago,
and the reason for that was "We don't have ability to know is call
still alive"
(http://lists.iptel.org/pipermail/serusers/2004-November/013035.html)
But, in April 2005, RFC 4028 (Session Timers in SIP) appeared, and
it (at least theoretically) can be utilised to achieve knowlege of active
dialogs, and, as result - on number of active calls.
And this RFC looks like supported on Cisco gateways:
U X.X.X.X:59104 -> X.X.X.X:5060
INVITE sip:aaaaaaa@X.X.X.X:5060 SIP/2.0.
Supported: 100rel,timer,replaces.
^^^^^
Min-SE: 1800.
^^^^^^^^^^^^^^
User-Agent: Cisco-SIPGateway/IOS-12.x.
Question: is this RFC/functionality planned to be supported in SER ?
If not - are there any good intro on "How to write SER module by yourself" ? :)
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
8 Aug
8 Aug
11 a.m.
Jiri Kuthan wrote:
You can write a ser script to implement session timer,
we have indeed done that.
Does that really work? Do you send reINVITEs from the SIP proxy?
Wouldn't then you have to change the CSeq of requests sent by the clients?
regards
klaus
That still does not give you access to call state. You
would have to write
own module which keeps it and hope that session timer will provide needed reliability
(which may not be always the case).
-jiri
At 12:26 01/08/2006, Alexandre Snarskii wrote:
Hi!
As far as I know, SER does not have functionality of limiting
number of calls on per-user basis. It was discussed years ago,
and the reason for that was "We don't have ability to know is call
still alive"
(http://lists.iptel.org/pipermail/serusers/2004-November/013035.html)
But, in April 2005, RFC 4028 (Session Timers in SIP) appeared, and
it (at least theoretically) can be utilised to achieve knowlege of active
dialogs, and, as result - on number of active calls.
And this RFC looks like supported on Cisco gateways:
U X.X.X.X:59104 -> X.X.X.X:5060
INVITE sip:aaaaaaa@X.X.X.X:5060 SIP/2.0.
Supported: 100rel,timer,replaces.
^^^^^
Min-SE: 1800.
^^^^^^^^^^^^^^
User-Agent: Cisco-SIPGateway/IOS-12.x.
Question: is this RFC/functionality planned to be supported in SER ?
If not - are there any good intro on "How to write SER module by yourself" ? :)
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers 
12:52 p.m.
Klaus Darilion wrote:
Jiri Kuthan wrote:
Either the UAC or the UAS sends session refresher requests according to
RFC 4028. The proxy just helps in setting up the session timer which can
be problematic if only one side supports this extension.
Miklos
You can write a ser script to implement session
timer, we have indeed
done that.
Does that really work? Do you send reINVITEs from the SIP proxy?
Wouldn't then you have to change the CSeq of requests sent by the clients?
regards
klaus
That still does not give you access to call
state. You would have to
write own module which keeps it and hope that session timer will
provide needed reliability
(which may not be always the case).
-jiri
At 12:26 01/08/2006, Alexandre Snarskii wrote:
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hi!
As far as I know, SER does not have functionality of limiting
number of calls on per-user basis. It was discussed years ago,
and the reason for that was "We don't have ability to know is call
still alive"
(http://lists.iptel.org/pipermail/serusers/2004-November/013035.html)
But, in April 2005, RFC 4028 (Session Timers in SIP) appeared, and
it (at least theoretically) can be utilised to achieve knowlege of
active dialogs, and, as result - on number of active calls.
And this RFC looks like supported on Cisco gateways:
U X.X.X.X:59104 -> X.X.X.X:5060
INVITE sip:aaaaaaa@X.X.X.X:5060 SIP/2.0.
Supported: 100rel,timer,replaces.
^^^^^
Min-SE: 1800.
^^^^^^^^^^^^^^
User-Agent: Cisco-SIPGateway/IOS-12.x.
Question: is this RFC/functionality planned to be supported in SER ?
If not - are there any good intro on "How to write SER module by
yourself" ? :)
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
1:01 p.m.
Miklos Tirpak wrote:
Klaus Darilion wrote:
Ok. This is rather easy.
regards
klaus
Jiri Kuthan wrote:
Either the UAC or the UAS sends session refresher requests according to
RFC 4028. The proxy just helps in setting up the session timer which can
be problematic if only one side supports this extension. You can write a ser script to implement session
timer, we have indeed
done that.
Does that really work? Do you send reINVITEs from the SIP proxy?
Wouldn't then you have to change the CSeq of requests sent by the
clients?
9 Aug
9 Aug
11:08 p.m.
At 10:00 08/08/2006, Klaus Darilion wrote:
Jiri Kuthan wrote:
yes
You can write a ser script to implement session
timer, we have indeed done that.
Does that really work? Do you send reINVITEs from the SIP proxy?
no. it would not be a proxy anymore then.
we just change the SIP messages in a way which stimulates PSTN gateways to use
session timers.
-jiri
Wouldn't then you have to change the CSeq of
requests sent by the clients?
regards
klaus
That still does not give you access to call state.
You would have to write own module which keeps it and hope that session timer will provide
needed reliability
(which may not be always the case).
-jiri
At 12:26 01/08/2006, Alexandre Snarskii wrote:
--
Jiri Kuthan http://iptel.org/~jiri/ Hi!
As far as I know, SER does not have functionality of limiting
number of calls on per-user basis. It was discussed years ago,
and the reason for that was "We don't have ability to know is call
still alive" (http://lists.iptel.org/pipermail/serusers/2004-November/013035.html)
But, in April 2005, RFC 4028 (Session Timers in SIP) appeared, and
it (at least theoretically) can be utilised to achieve knowlege of active dialogs, and, as
result - on number of active calls.
And this RFC looks like supported on Cisco gateways:
U X.X.X.X:59104 -> X.X.X.X:5060
INVITE sip:aaaaaaa@X.X.X.X:5060 SIP/2.0.
Supported: 100rel,timer,replaces.
^^^^^
Min-SE: 1800.
^^^^^^^^^^^^^^
User-Agent: Cisco-SIPGateway/IOS-12.x.
Question: is this RFC/functionality planned to be supported in SER ? If not - are there
any good intro on "How to write SER module by yourself" ? :)
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6682
days inactive
6690
days old
5 comments
4 participants
participants (4)
-
Alexandre Snarskii -
Jiri Kuthan -
Klaus Darilion -
Miklos Tirpak