[VoiceOps] Calls coming into our LRN

Hiers, David David_Hiers at adp.com
Tue Nov 9 09:56:42 EST 2010

BTW, thanks for the object lesson in overloading.  Someone succumbed an attack of the clevers, and now you've got a mess on your hands....

David Hiers

ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277

-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of lists at iamchriswallace.com
Sent: Monday, November 08, 2010 6:59 PM
To: Paul Timmins
Cc: VoiceOps
Subject: Re: [VoiceOps] Calls coming into our LRN

 Today we got hammered with calls from MetroPCS.  I will get a ticket 
 open with our LD carrier. Thanks again!


 On Mon, 08 Nov 2010 17:31:54 -0500, Paul Timmins <paul at timmins.net> 
> On 11/08/2010 04:37 PM, Chris Wallace wrote:
>> Years ago our switch tech decided to make our main company number 
>> the same as our LRN.  We have had an ongoing issue where calls to an 
>> LNP'd number do not come into our switch with the original called 
>> number and they are routed into our company PBX and we end up becoming 
>> the switchboard for people trying to reach our customers.  It seems as 
>> though we have been more and more of these calls lately.  Has anyone 
>> dealt with a similar issue? If so, what was your resolution?
> We have ours set up as RCFs to the network operations center so we
> know when there are LD providers stripping the generic address
> parameter, which would cause that. I've seen qwest do it a lot. :/
> It's not happening often enough to be a problem, but it seems to
> happen more on our LATA 344 customers.

VoiceOps mailing list
VoiceOps at voiceops.org

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

More information about the VoiceOps mailing list