What's worse really is not that you have to look at ILEC tandems out of
area - they don't perform any route filtering, if the originating caller
is calling out of area, it gets sent to their PIC/LPIC LD carrier.
So what you really need is every IXC in the country to make sure they
have a route to you either directly, through whatever tandem homing
arrangements you have, or via another IXC (really common especially in
rural areas to see a Level 3/Global Crossing hand off to
Qwest/AT&T/Verizon for the final termination.).
-Paul
On 07/15/2014 10:52 AM, Adam Vocks wrote:
So, at the very least, I need to start looking at each of the ILEC's
tandems in a specific LATA?
Adam
-----Original Message-----
From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Alex
Balashov
Sent: Tuesday, July 15, 2014 9:48 AM
To: voiceops@voiceops.org
Subject: Re: [VoiceOps] New Exchange 217/777
On 07/15/2014 10:44 AM, Adam Vocks wrote:
:-)
Take Kidd's call from Verizon in Colorado. If there isn't our
exchange in their local switch, do they forward the call on to another
switch in hopes that it will know where to send it? Similar to a
default gateway in IP world?
It would get kicked up to an ILEC tandem inside that LATA. There is
really no default gateway beyond that; at that point, you've already
exited into what the IP world would call "default route-free" or "Tier
1" routing space.
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
