On Thu, May 31, 2012 at 1:52 PM, Marc Carrafiello <[email protected]>wrote:
> OK so our head office has a Bell PRI connected to an Asterisk box. Our > Long Distance PIC is with Telus. Its been like this for 5 years, > everything is stable and working great, but then in mid-April I received 1+ > calling, rated with old DDD rates, on my Bell bill for the PRI. This bill > usually has no calling, except for non-1+ calls, like 411 and VSCs. > Hi Marc, That's definitely strange. I have one other thought as to how this could have happened, although it's not likely. I haven't tested it but I think it's possible to override your PIC with the 1010 prefix then the second carriers CIC. They used to use it for cheap LD services but I don't hear much about that anymore. As for why your PIC order didn't catch the traffic, IIRC my experience has been that when I add services to my account, like a new 1FL for a fax machine, I have to issue a new PIC order for that circuit. I've only had to do it a few times so you've probably got more experience in that area than me. If I had to bet, I'd lean the same way as you. It's probably a programming issue on the CO side. Maybe a typo caused one channel from someone else's circuit to be added to a trunk group on your account. It seems like that would be easier to do if you had NFAS on the PRI. You might check your PRI Debug for an error that says something "D channel says I have media on channel 49 but channel 49 could not be found." That's what I've seen on my systems in the past when the CO has more channels in a trunk group than I have defined on my side. Good luck getting to the bottom of that. I'd be curious to hear how it settles out. Usually you get a call back from Bell saying that they looked into it and nothing was wrong on their side, after which, the problem disappears. I usually interpret that to mean that the tech found the problem and fixed it but didn't want to 'fess up that it was his issue. All the best, Dave
