Alex,
I'm thinking that the location table in ser would do the trick - as max_contacts in the ser-0.9 registrar module seems to work well. The only problem with max_contacts is that it is a server-wide setting.
If you think about it, we really don't care about anything other than who has a contact AOR in the ser proxy because you can't really use your phone unless it's registered and we wouldn't let you register if you have exceeded you allowed number of location table records.
Unless there is someone out there with a way to do this in ser-0.9 then I'll just have to "AVPOPS-ize" the max_contacts piece of the registrar module myself.
As for "who our client is" -- we are a carriers-carrier. So our client is just another CLEC or other company that is selling VoIP and using our platform for their own customers.
Regards, Paul
--- Alex Rootham alex@blueslice.com wrote:
Hi Paul,
Remember that limiting the subscriber to one single SIP Registration at a time will only prevent the user from using two SIP devices *at the same time*. So all they would have to do is turn off their BT100 at home, and the X-ten registration would then work properly.
I can't really think of an easy way to ensure that the subscriber cannot use more then one device at all... what you're looking for is something like a MAC-address (in IP-world) or a SIM-id (in the GSM-world) that will uniquely identify the device-instance.
Alex Rootham Blueslice Newtorks
PS - I still haven't figured out who your client is, but if they offer VoIP, then they might be interested in becoming an MVNO. And if they already use SIP, and they want to be an MVNO, then they should definately be talking to Blueslice. I'm not sure if you're in a position to propose any biz-dev ideas to your client, but if you are, let me know and we can chat further...
Java Rockx wrote:
The reason is quite simple:
A business requirement for us is that a customer signs up for our service for say US$29.99
This US$29.99 entitles them to use **one** SIP phone and only one SIP phone. They cannot use
for
instance a Grandstream BT100 at home and X-ten at work - that is without paying for an
additional
"seat".
So I'm looking to alter the subscriber table and add a "seats" column with 1 being the default
and
0 meaning unlimited (which is the current ser default).
Regards, Paul
--- Daniel Liu daniel.liu@cu88.com wrote:
Why do you want this feature?
regards, Daniel
Java Rockx write:
Hi all.
Does anyone know if I can use avpops to dynamically set the registrar module's max_contacts parameter?
Regards, Paul
__________________________________ Do you Yahoo!? Send a seasonal email greeting and help others. Do good. http://celebrity.mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
__________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
__________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
If you think about it, we really don't care about anything other than who has a contact AOR in the ser proxy because you can't really use your phone unless it's registered and we wouldn't let you register if you have exceeded you allowed number of location table records.
Why would you say this? One does not have to be registered in order to generate INVITES. We have many users set up like this. Those that are wholesale and only need outbound calling are setup like that in our system.
Andres.
Sorry - My bad.
My assumption is that the mechanizm to determine the number of contacts for REGISTER messages would also be similar to the mechanism that determines INVITE eligiblity.
For example, if I get an INVITE I know who it's from. Now the question is does this INVITE come from someone who has a contact entry in the location table. If not - then reply with an error otherwise honor the INVITE.
The pseudo code would be something like this:
if (method=="REGISTER") {
if ([number of contacts] >= [max user seats for subscriber]) { return error code; break; }
// normal REGISTER logic follows }
// later in ser.cfg
if (method=="INVITE") {
if ([from contact not in location table]) { return error code; break; }
// normal INVITE logic follows }
So we are again back to dealing with just contact records for REGISTER and INVITEs. If someone registers their phone with 3600 seconds for the expiration and they have just one "seat" and then they decide to move their phone to a different network - then they'd be S.O.L. until their previous contact records expires.
Regards, Paul
--- Andres andres@telesip.net wrote:
If you think about it, we really don't care about anything other than who has a contact AOR in
the
ser proxy because you can't really use your phone unless it's registered and we wouldn't let
you
register if you have exceeded you allowed number of location table records.
Why would you say this? One does not have to be registered in order to generate INVITES. We have many users set up like this. Those that are wholesale and only need outbound calling are setup like that in our system.
Andres.
__________________________________ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Hi,
On Thursday 23 December 2004 00:22, Java Rockx wrote:
So we are again back to dealing with just contact records for REGISTER and INVITEs. If someone registers their phone with 3600 seconds for the expiration and they have just one "seat" and then they decide to move their phone to a different network - then they'd be S.O.L. until their previous contact records expires.
and when the routeable external IP of the NAT in front of the customer changes (e.g. because of some routine IP disconnect of the provider) he will not be reachable and can not make any calls until the old Contact expired?
BTW what are you doing with requests, to remove the existing binding (and afterwards I'll register a new Contact from my current location)?
Just my 2 cents... but I'll for sure not become your customer :-)
Regards Nils Ohlmeier
Regards, Paul
--- Andres andres@telesip.net wrote:
If you think about it, we really don't care about anything other than who has a contact AOR in
the
ser proxy because you can't really use your phone unless it's registered and we wouldn't let
you
register if you have exceeded you allowed number of location table records.
Why would you say this? One does not have to be registered in order to generate INVITES. We have many users set up like this. Those that are wholesale and only need outbound calling are setup like that in our system.
Andres.
Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I'm currently not doing anything. I'm just trying to find an answer to the problem.
I'm beginning to think that the ser community has no solution for such a problem. I know that other VoIP providers, such as Volo Communications, have such control over their networks and I'd be disappointed to think that there is something commercial software solves that open source cannot.
Regards, Paul
--- Nils Ohlmeier nils@iptel.org wrote:
Hi,
On Thursday 23 December 2004 00:22, Java Rockx wrote:
So we are again back to dealing with just contact records for REGISTER and INVITEs. If someone registers their phone with 3600 seconds for the expiration and they have just one "seat" and then they decide to move their phone to a different network - then they'd be S.O.L. until their previous contact records expires.
and when the routeable external IP of the NAT in front of the customer changes (e.g. because of some routine IP disconnect of the provider) he will not be reachable and can not make any calls until the old Contact expired?
BTW what are you doing with requests, to remove the existing binding (and afterwards I'll register a new Contact from my current location)?
Just my 2 cents... but I'll for sure not become your customer :-)
Regards Nils Ohlmeier
Regards, Paul
--- Andres andres@telesip.net wrote:
If you think about it, we really don't care about anything other than who has a contact AOR in
the
ser proxy because you can't really use your phone unless it's registered and we wouldn't let
you
register if you have exceeded you allowed number of location table records.
Why would you say this? One does not have to be registered in order to generate INVITES. We have many users set up like this. Those that are wholesale and only need outbound calling are setup like that in our system.
Andres.
Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
__________________________________ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Hi
why not forcing the re-registering to a low timing, like 3 minutes? if would take much more than that to move the phone to another network...
Cheers !3runo
Java Rockx wrote:
I'm currently not doing anything. I'm just trying to find an answer to the problem.
and when the routeable external IP of the NAT in front of the customer changes (e.g. because of some routine IP disconnect of the provider) he will not be reachable and can not make any calls until the old Contact expired?
I'm sure it is possible with open source software. In (this) case you (probably) have to add a little bit of code. But IMO your asking for "features" which are restricting the users of your service (compared to what the protocol and other providers offer). And as open source developers typically love their freedom (thats one of the advantages of OS) they usually do not volunteer to implement any kind of user restrictions expect it is for security reasons.
Note: this is just my personal opinion.
Greetings Nils
On Thursday 23 December 2004 01:03, Java Rockx wrote:
I'm currently not doing anything. I'm just trying to find an answer to the problem.
I'm beginning to think that the ser community has no solution for such a problem. I know that other VoIP providers, such as Volo Communications, have such control over their networks and I'd be disappointed to think that there is something commercial software solves that open source cannot.
Regards, Paul
--- Nils Ohlmeier nils@iptel.org wrote:
Hi,
On Thursday 23 December 2004 00:22, Java Rockx wrote:
So we are again back to dealing with just contact records for REGISTER and INVITEs. If someone registers their phone with 3600 seconds for the expiration and they have just one "seat" and then they decide to move their phone to a different network - then they'd be S.O.L. until their previous contact records expires.
and when the routeable external IP of the NAT in front of the customer changes (e.g. because of some routine IP disconnect of the provider) he will not be reachable and can not make any calls until the old Contact expired?
BTW what are you doing with requests, to remove the existing binding (and afterwards I'll register a new Contact from my current location)?
Just my 2 cents... but I'll for sure not become your customer :-)
Regards Nils Ohlmeier
Regards, Paul
--- Andres andres@telesip.net wrote:
If you think about it, we really don't care about anything other than who has a contact AOR in
the
ser proxy because you can't really use your phone unless it's registered and we wouldn't let
you
register if you have exceeded you allowed number of location table records.
Why would you say this? One does not have to be registered in order to generate INVITES. We have many users set up like this. Those that are wholesale and only need outbound calling are setup like that in our system.
Andres.
Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers