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" ? :)
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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Klaus Darilion wrote:
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?
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
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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/ _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Miklos Tirpak wrote:
Klaus Darilion wrote:
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?
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.
Ok. This is rather easy.
regards klaus
At 10:00 08/08/2006, Klaus Darilion wrote:
Jiri Kuthan wrote:
You can write a ser script to implement session timer, we have indeed done that.
Does that really work?
yes
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:
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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/ _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
-
Alexandre Snarskii -
Jiri Kuthan -
Klaus Darilion -
Miklos Tirpak