Send VoiceOps mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Cisco ITP IOS (Joe Fratantoni)
2. Direct CLEC interconnect - taking the plunge (Jay Hennigan)
3. Re: Direct CLEC interconnect - taking the plunge (Anthony Orlando)
4. Re: Direct CLEC interconnect - taking the plunge (Ryan Finnesey)
5. Re: Cisco ITP IOS (Peter Childs)
6. Re: Direct CLEC interconnect - taking the plunge (Scott Berkman)
7. Re: Direct CLEC interconnect - taking the plunge (Alex Balashov)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Oct 2012 15:14:36 -0600
From: Joe Fratantoni <[email protected]>
To: <[email protected]>
Subject: [VoiceOps] Cisco ITP IOS
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hey Guys,
We're looking for the Cisco IOS ITP release from 2011;
any clue on how we might be able to obtain such a thing?
Thanks,
Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121017/66297a36/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 17 Oct 2012 16:39:06 -0700
From: Jay Hennigan <[email protected]>
To: VoiceOps <[email protected]>
Subject: [VoiceOps] Direct CLEC interconnect - taking the plunge
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
We are a regional hosted VoIP provider in California. We started as an
ISP and moved into becoming a CLEC offering VOIP. As is probably the
case with most, we started buying DIDs from wholesale carriers as SIP
trunks. The majority of our customers are within a single LATA with a
large minority in an adjoining one.
We are investigating the feasibility of direct interconnect with the
RBOC/ILEC via SS7.
I'm interested in pointers/gotchas as well as recommendations of a
consultant to help us navigate the maze, both from a political and
technical standpoint. Suggestions as what not to do or who not to hire
are also welcome.
Please feel free to respond on-list or off as you feel appropriate.
--
------------------------------
Message: 3
Date: Wed, 17 Oct 2012 19:13:05 -0500
From: Anthony Orlando <[email protected]>
To: Jay Hennigan <[email protected]>
Cc: VoiceOps <[email protected]>
Subject: Re: [VoiceOps] Direct CLEC interconnect - taking the plunge
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Backup Telecom would be my first choice. Mary Lou Carey. She's on this board.
On Oct 17, 2012, at 18:39, Jay Hennigan <[email protected]> wrote:
> We are a regional hosted VoIP provider in California. We started as an
> ISP and moved into becoming a CLEC offering VOIP. As is probably the
> case with most, we started buying DIDs from wholesale carriers as SIP
> trunks. The majority of our customers are within a single LATA with a
> large minority in an adjoining one.
>
> We are investigating the feasibility of direct interconnect with the
> RBOC/ILEC via SS7.
>
> I'm interested in pointers/gotchas as well as recommendations of a
> consultant to help us navigate the maze, both from a political and
> technical standpoint. Suggestions as what not to do or who not to hire
> are also welcome.
>
> Please feel free to respond on-list or off as you feel appropriate.
> --
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
Message: 4
Date: Thu, 18 Oct 2012 00:18:32 +0000
From: Ryan Finnesey <[email protected]>
To: Anthony Orlando <[email protected]>
Cc: VoiceOps <[email protected]>
Subject: Re: [VoiceOps] Direct CLEC interconnect - taking the plunge
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Backup Telecom is great.
Sent from my iPad
On Oct 17, 2012, at 8:14 PM, "Anthony Orlando" <[email protected]> wrote:
> Backup Telecom would be my first choice. Mary Lou Carey. She's on this board.
>
> On Oct 17, 2012, at 18:39, Jay Hennigan <[email protected]> wrote:
>
>> We are a regional hosted VoIP provider in California. We started as an
>> ISP and moved into becoming a CLEC offering VOIP. As is probably the
>> case with most, we started buying DIDs from wholesale carriers as SIP
>> trunks. The majority of our customers are within a single LATA with a
>> large minority in an adjoining one.
>>
>> We are investigating the feasibility of direct interconnect with the
>> RBOC/ILEC via SS7.
>>
>> I'm interested in pointers/gotchas as well as recommendations of a
>> consultant to help us navigate the maze, both from a political and
>> technical standpoint. Suggestions as what not to do or who not to hire
>> are also welcome.
>>
>> Please feel free to respond on-list or off as you feel appropriate.
>> --
>> _______________________________________________
>> VoiceOps mailing list
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
------------------------------
Message: 5
Date: Wed, 17 Oct 2012 23:52:15 +0000
From: Peter Childs <[email protected]>
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Cisco ITP IOS
Message-ID: <cca588ab.17787%[email protected]>
Content-Type: text/plain; charset="us-ascii"
Cisco ?
I believe the 2811 ITP and 72xx/76xx are still supported, although 2811 may be
end-of-sale
From: Joe Fratantoni
<[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Date: Thursday, 18 October 2012 7:44 AM
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [VoiceOps] Cisco ITP IOS
Hey Guys,
We're looking for the Cisco IOS ITP release from 2011; any clue on how we might
be able to obtain such a thing?
Thanks,
Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121017/c0ccf1fd/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 17 Oct 2012 23:19:44 -0400
From: "Scott Berkman" <[email protected]>
To: "'Ryan Finnesey'" <[email protected]>, "'Anthony Orlando'"
<[email protected]>
Cc: 'VoiceOps' <[email protected]>
Subject: Re: [VoiceOps] Direct CLEC interconnect - taking the plunge
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Agreed on Mary Lou, she knows her stuff and can help navigate the waters
especially when it comes to ordering.
Some questions you may want to ask yourself:
Why make the step? Are there features or capabilities you are missing, or
just a lack of control you want to address? Does this make business sense
after adding up all the different recurring and start-up costs?
Do you have the right geographical concentration for this to make sense
(from the OP sounds like you might).
Do you and/or your staff have SS7 knowledge and equipment that can handle it
already? Neither of these are particularly cheap.
Do you have an understanding of the local PUC's working rules and what it
will take to get a CLEC license? Is this even possible in your specific
situation (some PUCs are very tight on issuing new licenses)?
Do you have a good telecom Attorney that can help you interpret and
negotiate your ICA with the iLEC? Do you know who else is in the market to
compare their ICA?
Do you understand the local LEC infrastructure including how many LATAs,
Tandems, RC, and different LECs you may need to interconnect to? Is there
more than one iLEC covering the areas you wish to serve?
Are you planning for Tandem trunking or do you have a reason to build out
End-office trunks? What are your capacity needs?
Do you have a staff to handle LNP, 911, and other "provisioning" tasks? How
about systems to track it all? The FCC now has turnaround requirements on
simple ports as low as one day you'll need to be able to meet.
What are you not going to handle on your own? TF RESPORG is one good
example that smaller CLECs don't jump right into. You'll still need other
carriers for LD and International as well.
Have you taken into account supplementary services like e911 (you'll need a
listing provider like Intrado if you plan to have local trunks, or a nomadic
solution like Bandwidth/Dash/iNetwork and 911-enable), OSDA, CNAM and LNP
dipping?
Some other items you'll want to research include the costs and processes for
getting the other details setup, like switch CLLIs, point codes, OCNs, TN
block assignments...
Hope that helps,
-Scott
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Ryan Finnesey
Sent: Wednesday, October 17, 2012 8:19 PM
To: Anthony Orlando
Cc: VoiceOps
Subject: Re: [VoiceOps] Direct CLEC interconnect - taking the plunge
Backup Telecom is great.
Sent from my iPad
On Oct 17, 2012, at 8:14 PM, "Anthony Orlando" <[email protected]> wrote:
> Backup Telecom would be my first choice. Mary Lou Carey. She's on this
board.
>
> On Oct 17, 2012, at 18:39, Jay Hennigan <[email protected]> wrote:
>
>> We are a regional hosted VoIP provider in California. We started as an
>> ISP and moved into becoming a CLEC offering VOIP. As is probably the
>> case with most, we started buying DIDs from wholesale carriers as SIP
>> trunks. The majority of our customers are within a single LATA with a
>> large minority in an adjoining one.
>>
>> We are investigating the feasibility of direct interconnect with the
>> RBOC/ILEC via SS7.
>>
>> I'm interested in pointers/gotchas as well as recommendations of a
>> consultant to help us navigate the maze, both from a political and
>> technical standpoint. Suggestions as what not to do or who not to hire
>> are also welcome.
>>
>> Please feel free to respond on-list or off as you feel appropriate.
>> --
>> _______________________________________________
>> VoiceOps mailing list
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
Message: 7
Date: Wed, 17 Oct 2012 23:40:54 -0400
From: Alex Balashov <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] Direct CLEC interconnect - taking the plunge
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 10/17/2012 11:19 PM, Scott Berkman wrote:
> Why make the step? Are there features or capabilities you are missing, or
> just a lack of control you want to address? Does this make business sense
> after adding up all the different recurring and start-up costs?
Especially high emphasis on this one--the most important of them all.
Good call!
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
End of VoiceOps Digest, Vol 40, Issue 19
****************************************
