I can't see how you can do that with sipXecs. You might be able to limit calls between physical sites with a Session Border Controller.
If you don't mind me asking, why would you want limit the number of calls within a site? I can understand between sites due to bandwidth concerns. Mike > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sipx-users- > [EMAIL PROTECTED] On Behalf Of Pieter Lauwers > Sent: Thursday, December 11, 2008 7:20 AM > To: [email protected] > Subject: [sipx-users] Limiting the number of simultaneous calls for a > groupof users > > Hello, > > In our setup there are several physical networks with on each network a > group of users. Each network can only guarantee a limited number of > VoIP > calls and we would like the SipX server to enforce these limits. > > To that extend we should be able to define the maximum number of calls > that can be active at the same time per group. Actually we should be > able to limit the number of active users per group. A call between two > users of the same group would count for 2 active users in the group and > a call between users of two different groups would count as one active > user for the one group and one active user for the next group. > > A second question related to the first one is the issue of never ending > calls. If for some reason the BYE message is lost, the call will remain > active forever (or until the SipX server is rebooted). This would be > treated as active users and as such impact the number of simultaneous > calls. Is there a way to detect idle calls or just to terminate any > call > that is active for more than let's say 12 hours? > > Thanks > Pieter > > > *** e-mail confidentiality footer *** > This message and any attachments thereto are confidential. They may > also > be privileged or otherwise protected by work product immunity or other > legal rules. If you have received it by mistake, please let us know by > e-mail reply and delete it from your system; you may not copy this > message or disclose its contents to anyone. > E-mail transmission cannot be guaranteed to be secure or error free as > information could be intercepted, corrupted, lost, destroyed, arrive > late or incomplete, or contain viruses. The sender therefore is in no > way liable for any errors or omissions in the content of this message, > which may arise as a result of e-mail transmission. If verification is > required, please request a hard copy. > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
