*shrugs* I didn't build it.
That's also why I said it didn't make any sense. To me, no traffic would match being 8YY *AND* to this ratecenter, at least from my perspective. Therefore, that rule would never apply. That said, toll-free dipping is a new concept to me that I'll have to read up about. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Paul Timmins" <p...@timmins.net> To: voiceops@voiceops.org Sent: Thursday, July 1, 2021 11:10:14 AM Subject: Re: [VoiceOps] 8YY Traffic On 7/1/21 11:20 AM, Mike Hammett wrote: Is there any reason I can't throw all 8YY traffic at my IXC tandem? In looking in my Metaswitch config, it appears that only 8YY traffic destined for my LATA (which doesn't really make any sense) goes to the tandem. Everything else goes out to a domestic termination provider. How does your switch know that the 8YY in question is destined for your LATA? I mean, you have to provide a valid path in the LATA for the CICs that might come back based on your source TN, like if you're calling from NPA 248, you should have that sent somewhere in LATA 340 in case the SMS/800 has a specific cutout for various LATAs to use certain CICs (for example, I use Inteliquent's FGD code in areas where Inteliquent has built it out, but not in other LATAs where Inteliquent hasn't built out, so dipping LATA 340 (Detroit) and then terminating the call to a local tandem in rural idaho isn't going to work well!) That's the only caveat I'm aware of you need to concern yourself with - that the CICs returned from your toll free dip are going to be valid for the tandem you are connected to, more or less. _______________________________________________ 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
