Re: BillMax questions -- New service provisioning for multiple existing services. Advice?

["Brandon Floyd" <beernut@cei.net>]

seems to be a few sentences missing from my post.

Once you do what I described below you can setup your new service to have 3 
fields
d01 - username
d02 - password
d03 - voip number

Thats the way I would do it. You would probably end up with 2 voip scripts, 
1 for the current voip only service, 2nd for the new voip / radius / email 
service that uses the d03 field.

That would atleast keep you from not having to add 2 services to the 
account.

-bn



----- Original Message ----- 
From: "Brandon Floyd" <beernut@cei.net>
To: "Ray Van Dolson" <rayvd@digitalpath.net>; <questions@billmax.com>
Sent: Tuesday, November 08, 2005 11:57 AM
Subject: Re: BillMax questions -- New service provisioning for multiple 
existing services. Advice?


> Would think the easiest way would be to just define a new resource bit for 
> the service to use. Then in your service_hook have a defined entry for 
> that resource bit and do what needs to be done. That should be the easiest 
> solution out of what you mentioned. Your service_hook would basically be 
> doing what your radius/email and voip does. So shouldnt be that much more 
> work for you to do.
>
> -bn
>
>
> ----- Original Message ----- 
> From: "Ray Van Dolson" <rayvd@digitalpath.net>
> To: <questions@billmax.com>
> Sent: Tuesday, November 08, 2005 11:26 AM
> Subject: BillMax questions -- New service provisioning for multiple 
> existing services. Advice?
>
>
>> Our current Billmax setup has resource bits for Email, Radius accounts 
>> and
>> Voice over IP accounts.  We have service definitions that provision for 
>> Email
>> & Radius together and a separate service definition for Voice over IP.
>>
>> However, the sales guys would like to offer a new package -- a package
>> offering both VoIP and Radius/Email in one.
>>
>> I'm trying to figure out a good, clean way to set this up.  Since 
>> initially we
>> have two separate services, I have overlapping usage of d01 fields in my
>> service hook definitions.
>>
>> In other words, a d01 field for the normal Radius/Mail servdef is
>> username@domain.  For a VoIP servdef the d01 field is a 10 digit phone 
>> number.
>>
>> Obviously, when the provisioning hooks run, chaos results. :-)
>>
>> I'm thinking the easiest solution is to divide our new service offering 
>> into
>> two separate servdef's and just let people know they need to add both to 
>> an
>> account.  Would there be any way to enforce this?
>>
>> The other option I guess would be to create a new resource bit whose
>> provisioning scripts work with different fields than the original ones do 
>> so I
>> could have both the VoIP username and normal username in the same servdef
>> definition.
>>
>> I can think of some other, crazier hacky ways to do this, but I'd like to 
>> keep
>> this as sensible a setup as possible.  To keep my resource bits 
>> consistent in
>> their meanings (in other words, so a lot of external mysql scripts don't 
>> have
>> to be modified), I'm thinking just adding two seperate servdef's would be 
>> the
>> easiest solution.  It would definitely be nice of there was a way to 
>> require
>> that both were present under a User though somehow.
>>
>> Thanks for any thoughts.
>>
>> Ray
>>
>> -- 
>> Ray Van Dolson
>> Linux/Unix Systems Administrator
>> Digital Path, Inc.
>> -----------------------------------------------------------------------------
>> To unsubscribe from the "BillMax Questions" mailing list, please
>> send a message to "majordomo@billmax.com" with "unsubscribe questions"
>> in the message body. The message must be sent from the exact email
>> address on the list.
>>
>
> -----------------------------------------------------------------------------
> To unsubscribe from the "BillMax Questions" mailing list, please
> send a message to "majordomo@billmax.com" with "unsubscribe questions"
> in the message body. The message must be sent from the exact email
> address on the list.
> 

-----------------------------------------------------------------------------
To unsubscribe from the "BillMax Questions" mailing list, please
send a message to "majordomo@billmax.com" with "unsubscribe questions"
in the message body. The message must be sent from the exact email
address on the list.