I wanted to note that I am still interested in working with competitive tandem providers for "on-net" calls... calls among their customers, without ever hitting an ILEC tandem.
Also, now that I look at their web page... it says it allows me to receive both local and long distance calls using that service... which seems to conflict with what the sales guy told me. *sigh* ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Mike Hammett" <[email protected]> To: "VoiceOps" <[email protected]> Sent: Friday, August 9, 2019 2:42:37 PM Subject: [VoiceOps] Connecting to Remote Tandems I'm evaluating methods of extending our footprint. I purposely left out company names. One of the companies we talked to was really only interested in getting us the inbound long distance calls, not the local ones. Well, they would, but the terms were vastly different. Given that I still need to build out to connect to the local tandem, what's the point in using a third party to connect to long distance? Are the terms for connecting to the local tandems different because the access tandem is simpler, whereas the local tandem could potentially involve connections to a bunch of other switches, once volume dictated I needed direct connections... and they don't want to deal with that? Are there third parties that don't have vastly different terms for local tandem services? Also, is it likely that I just don't understand what's going on? I went circles with the sales rep to make sure I understood what he was saying, but I could be wrong. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
