
Correct - I've had a few try to convince us that they themselves required an ICA but they generally backed down from that. You should really have a formal relationship with ILECs anyway, if you'll be porting from them. You have OSS systems you'll want access to for LSRs/CSRs and ticket opening, and you'll want to get accessable letters for things that might affect your relationships or routing. If you're going to do this multi-ILEC thing, make sure both ICAs include something about traffic from other ILECs transiting their tandems. -Paul On 06/16/2011 07:19 PM, Eric Hiller wrote:
Ah, so it is just CLECs ala Level 3 and XO that let us do this then?
-Eric
On Thu, June 16, 2011 6:15 pm, Paul Timmins wrote:
No ILEC I've ever seen will let you port without an ICA
On 06/16/2011 07:12 PM, Eric Hiller wrote:
Carlos,
But what if you were in a LATA where ATT is and you have no ICA with ATT just some other ILEC in the LATA? Are you saying that ATT would not allow you to port any numbers from them without an ICA?
-Eric
On Thu, June 16, 2011 5:30 pm, Carlos Alcantar wrote:
Eric,
We just went through this battle with att we thought the same but reading deep into our ICA we had to get minimum trunks to all the tandems in the lata 2x t1's and then we ordered the majority of our trunking at the tandem where we homed our LRN. It sucks but we haven't found a way around it.
Carlos Alcantar Race Communications / Race Team Member 101 Haskins Way, So. San Francisco, CA. 94080 Phone: +1 415 376 3314 Fax: +1 650 246 8901 / carlos *at* race.com / www.race.com<http://www.race.com/>
On 6/16/11 2:02 PM, "Eric Hiller"<clec at cygnustel.com> wrote:
I would not think you would need trunks to all the tandems in the lata for TERMINATIONS though, just ORIGINATIONS as Mary Lou had said?
For example I can port a number from Level 3 even though I am not on every tandem in the LATA now.
Is this correct Mary Lou? So if I added 4 new LATAs and I just wanted to do terminations, I would just have to establish a new LRN in each LATA as well as trunking to the tandem my LRN is homed on?
-Eric
On Wed, June 15, 2011 5:59 pm, Carlos Alcantar wrote:
Mary Lou,
At least here in CA att makes you trunk to all the tandems in the lata. At least with min trunks and you build your bulk of your trunks where your LRN is going to sit at.
Carlos Alcantar Race Communications / Race Team Member 101 Haskins Way, So. San Francisco, CA. 94080 Phone: +1 415 376 3314 Fax: +1 650 246 8901 / carlos at race.com / www.race.com<http://www.race.com/>
On 6/15/11 10:55 AM, "Mary Lou Carey"<marylou at backuptelecom.com> wrote:
> To terminate traffic you only need to have trunking to the LRN > tandem > in > that LATA, but to originate traffic you need to have trunking > established > to > the tandem that the rate center of the NXX homes on. Once we have > all > your > Chicago trunks installed, you will be able to port any number in the > LATA > to > yourself. Make sense? > > > Mary Lou Carey > BackUP Telecom Consulting > CLEC Consultant > OFF: 615-791-9969 > > > > > -----Original Message----- > From: voiceops-bounces at voiceops.org > [mailto:voiceops-bounces at voiceops.org] > On Behalf Of Eric Hiller > Sent: Wednesday, June 15, 2011 10:50 AM > To: voiceops at voiceops.org > Subject: [VoiceOps] Porting Number - CLEC > > In order to port a number, what trunking requirements do we have? Is > it > that we have to have trunking to the same tandem as the npa-nxx > holder? > IE. If I wanted to port 100-100-1000 And the 100-100-1 thousands > block > is > held by company A, and then 100-100 npanxx/ten k block is held by > Company > B and is homed on Tandem C, then I just need to have trunking into > Tandem > C and have an ICA with whomever controls Tandem C, which could be > company > A,B or some third company C correct? > > The same would apply in order to get our own thousands block as well > correct? > > Thanks, > -Eric Hiller > Cygnus > > > > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > > >
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops