Does anybody know what is is involved in reslling DSL service? Not just selling for phone company but reselling as your own. Do you need to set anything up on your end? What do you have to have/configure? What parts are managed by phone company and what isnt?
Reselling DSL
- Thread starter SolarisGuru
- Start date
LOL.
Dont mean cheatting out phone company. I mean reselling their DSL. As all the DSl providers go through the phone company (lease the lines) So I was wondering how this was done. And what was involved
Dont mean cheatting out phone company. I mean reselling their DSL. As all the DSl providers go through the phone company (lease the lines) So I was wondering how this was done. And what was involved
Maybe im not communicating properly. I dont mean reselling DSL that I have at my location. I mean Having a business that provides DSL to customers. How would I go about this. What materials/costs/configuratioon involved regarding.
1. get a trench digger so you can dig trenches down the road and lay wire and/or fiber to your customers (cable and phone companies already have this in place for their own use...) Be sure to get city and state permits to do this!
2. Purchase an agreement with an internet backbone provider. Could be phone or cable company, but they won't like competitors...
3. Dig a trench and lay some fiber to connect to the backbone provider.
4. Dig more trenches to have backup fiber connections to your backbone provider and also any critical places like switch stations and such.
5. Make sure your main switch system is super fast and well built.
6. Try to find customers willing to pay enough money to cover your investment... good luck...
7. Oh, and don't forget to hire some helpdesk folks to provide customer service to the idiot users who won't know how to get their computers on the internet...
If you want to go a simpler way, you could do like some smaller DSL providers and piggyback on the main phone company. I'm not sure exactly how they do it, but I'd bet they have to pay some money to the telco in order to get the connection to the customers and use the wires.
Have fun!
2. Purchase an agreement with an internet backbone provider. Could be phone or cable company, but they won't like competitors...
3. Dig a trench and lay some fiber to connect to the backbone provider.
4. Dig more trenches to have backup fiber connections to your backbone provider and also any critical places like switch stations and such.
5. Make sure your main switch system is super fast and well built.
6. Try to find customers willing to pay enough money to cover your investment... good luck...
7. Oh, and don't forget to hire some helpdesk folks to provide customer service to the idiot users who won't know how to get their computers on the internet...
If you want to go a simpler way, you could do like some smaller DSL providers and piggyback on the main phone company. I'm not sure exactly how they do it, but I'd bet they have to pay some money to the telco in order to get the connection to the customers and use the wires.
Have fun!
I do it under my own brand for my consulting company.
We found a local ISP that has a provider agreement with a telco, they hadle the circuits and the Internet connection. We find the customers, set them up, and provide the support and billing. Basically we put in an order to our ISP to set up the line, and they deal with the telco in the region and get it all set up, then it's ours from then on. We just pay a flat rate per user we set up per month.
It's nice in that we don't have to maintain the connection to the telco, or the connection to the Internet, and if we rule out the configuration or the modem on the end user side, we escalate it to them and they deal directly with the telco. Since they are a big client instead of just a home user, typically lines get fixed quite a bit faster.
We don't make as much money as if we were doing all of it on our own, but we also didn't have to come up with $100k to get started.
We found a local ISP that has a provider agreement with a telco, they hadle the circuits and the Internet connection. We find the customers, set them up, and provide the support and billing. Basically we put in an order to our ISP to set up the line, and they deal with the telco in the region and get it all set up, then it's ours from then on. We just pay a flat rate per user we set up per month.
It's nice in that we don't have to maintain the connection to the telco, or the connection to the Internet, and if we rule out the configuration or the modem on the end user side, we escalate it to them and they deal directly with the telco. Since they are a big client instead of just a home user, typically lines get fixed quite a bit faster.
We don't make as much money as if we were doing all of it on our own, but we also didn't have to come up with $100k to get started.
Thank you, MysticlLama (and everyone else)
That is how I want to do it. Sorry to everyone else if I wasnt clear enough.
MysticLlama, Do your users know the ISP they are using or do you have it that everything goes through you (Does your ISP ever contact them directly other than when you consult ISP for escalations?) Do your users emails show up as user@isp.com our do you offer them domain based email(ISP mail server or in house?).
Geez man, if you need to ask a question similar to "can they have their own Domain name?", maybe you don't need to be going into the IPS business...
Just my .0002
Just my .0002
Maybe you should read it again, that wasnt my question. My question was does he offer domain name email instead of users having the generic something@isp.com that would let the end user know what carrier other than telco he is using.
Please be advised your qoute is wrong "can they have their own Domain name?" was never asked
I would ask that any responses be to help me in this issue not to belittle me for asking.
Right now e-mail is completely based on the customer. The few customers we have are businesses that already had servers in place and run their own e-mail. We do all static IPs, so it's never a problem with DNS or anything.
There are a couple of individuals that are signed up, but they are "prosumers" that either run their own servers, or wouldn't use an ISP e-mail address anyway.
We plan to eventually have a mailserver up for our customers, but since we haven't been doing a lot of hookups to the public yet, it's not at the top of the priority list. Most of the people we hooked up are already clients in another respect, and this is just another part of their service contract or added to their billings.
The could tell what the actual telco is I suppose if they looked closely at their online account that's tied to their telephone line (at least in the case of Qwest customers), because it shows the "actual" ISP that they are with, but since the ISP itself doesn't offer DSL under their main name, going to the site wouldn't really get them a lot of info anyhow.
We originally set up all the contracts with the ISP to do small DSL-connected WANs, but figured we may as well provide DSL to some of our customers too since we could. Since we are managing the connections more closely than a random ISP would... i.e. we run thier servers/networks as well, we don't really need to have services in place just yet like Covad/Speakeasy/Whatever ISP would.
There are a couple of individuals that are signed up, but they are "prosumers" that either run their own servers, or wouldn't use an ISP e-mail address anyway.
We plan to eventually have a mailserver up for our customers, but since we haven't been doing a lot of hookups to the public yet, it's not at the top of the priority list. Most of the people we hooked up are already clients in another respect, and this is just another part of their service contract or added to their billings.
The could tell what the actual telco is I suppose if they looked closely at their online account that's tied to their telephone line (at least in the case of Qwest customers), because it shows the "actual" ISP that they are with, but since the ISP itself doesn't offer DSL under their main name, going to the site wouldn't really get them a lot of info anyhow.
We originally set up all the contracts with the ISP to do small DSL-connected WANs, but figured we may as well provide DSL to some of our customers too since we could. Since we are managing the connections more closely than a random ISP would... i.e. we run thier servers/networks as well, we don't really need to have services in place just yet like Covad/Speakeasy/Whatever ISP would.
SolarisGuru, there are two approaches that you might practically take. One approach is to be a straight reseller for a DSL ISP. The service would be entirely provided by the ISP, you simply do the sales job and get a partner commission on the sale. This is typically the best business arrangement, low start-up cost on your side and if you start doing real volume you can get inside contacts at the ISP who'll give you better support and allow you to add some value for your customers.
Another approach would be to be your own ISP on top of some DCLEC. They all have different requirements, but generally speaking the minimum would be for you to pull a full T1 running Frame Relay or ATM (depending on carrier) from their L2 network to your router, and you'll need to set up to be able to work with their provisioning system. There are a lot of detailed technical requirements for each DCLEC and the ones I've worked with are NDA material, so I can't say more. They also typically these days have explicit dollar volume requirements (you must generate so much revenue paid to them) and implicitly the rates you get for the DSL circuit and L2 backhaul are usually terrible until you do a lot of volume (that is to say, your cost for just the DSL circuit and L2 to you will typically be noticeably higher than it would cost to get the whole thing with ISP service from the DCLEC's preferred ISPs unless you're doing a huge volume).
Technically speaking you could attempt to become a DCLEC yourself, which would require you to get CO colocation space, CO certification, and some set of regulatory licenses. There are some exceptions (alarm loop hacks and such) but generally speaking, the up-front cost of doing this would put it out of the reach of I think everyone in this forum. Legal fees alone will be huge.
Another approach would be to be your own ISP on top of some DCLEC. They all have different requirements, but generally speaking the minimum would be for you to pull a full T1 running Frame Relay or ATM (depending on carrier) from their L2 network to your router, and you'll need to set up to be able to work with their provisioning system. There are a lot of detailed technical requirements for each DCLEC and the ones I've worked with are NDA material, so I can't say more. They also typically these days have explicit dollar volume requirements (you must generate so much revenue paid to them) and implicitly the rates you get for the DSL circuit and L2 backhaul are usually terrible until you do a lot of volume (that is to say, your cost for just the DSL circuit and L2 to you will typically be noticeably higher than it would cost to get the whole thing with ISP service from the DCLEC's preferred ISPs unless you're doing a huge volume).
Technically speaking you could attempt to become a DCLEC yourself, which would require you to get CO colocation space, CO certification, and some set of regulatory licenses. There are some exceptions (alarm loop hacks and such) but generally speaking, the up-front cost of doing this would put it out of the reach of I think everyone in this forum. Legal fees alone will be huge.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter