I have seventeen offices total. Two of these offices can call each other and it's considered a local call, although they're in different NPAs. We just installed a new PRI from a new carrier in one of these offices. This other office was unable to call them after that. They just got RELEASE AND TRY AGAIN. New carrier told me that happened because old carrier didn't release all the DIDs in their range. But if that was true, how come all other fifteen offices were able to call new carrier PRI office with no problem? I can't help but think that this was new carrier's fault. It took six hours for them to resolve this, and the CEO is livid and wants to know how it is this happened. Could new carrier have misprogrammed the NXX or something? Your assistance is appreciated. Thank you.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
unable to call from one office to another over new T1
- Thread starter coniglio
- Start date
let me take a shot at this one.
office a gets a new carrier,
office b could, but now can't call office a.
all other offices can call office a.
no other software was touched.
your point is correct, it c can call a then the dids are pointed right... it took six hours for them to solve this, them= new carrier provider?.. btw 6 hrs would be timer for shift change, different software tech fixes problem in 30 sec. if the new carrier fixed the problem, it was there problem, period. if the new pipe(t1)works from office c to office a, it works. Release and try again on screen would make the trouble seem to be in the originating switch, i would have tried acod then digits to isolate that, if you use enl msgi/o (ld 96) on your d, you can see who refused the call. you didn't mention CDP, are you dialling 8 digits between offices? are your switches networked or just tied together with local pri/t1's/cots.. without being there when the problem was happening, it was your new carrier, Software problems are normally fixed in 10 seconds, sometimes it takes us 5 hours and 59 minutes to find where it broke. we both know that no one was programing for 6 hours to rebuild a data base. with no other evidence, your new carrier is 100 per cent at fault. to avoid this problem i install new pri's, test then retest then have the did's rerouted in the dax then test and use for a week then take the old t's out. the cost is nothing compared to some systems being down for ? hours. i've seen it take days. not a pretty site.
john poole
bellsouth business
columbia,sc
office a gets a new carrier,
office b could, but now can't call office a.
all other offices can call office a.
no other software was touched.
your point is correct, it c can call a then the dids are pointed right... it took six hours for them to solve this, them= new carrier provider?.. btw 6 hrs would be timer for shift change, different software tech fixes problem in 30 sec. if the new carrier fixed the problem, it was there problem, period. if the new pipe(t1)works from office c to office a, it works. Release and try again on screen would make the trouble seem to be in the originating switch, i would have tried acod then digits to isolate that, if you use enl msgi/o (ld 96) on your d, you can see who refused the call. you didn't mention CDP, are you dialling 8 digits between offices? are your switches networked or just tied together with local pri/t1's/cots.. without being there when the problem was happening, it was your new carrier, Software problems are normally fixed in 10 seconds, sometimes it takes us 5 hours and 59 minutes to find where it broke. we both know that no one was programing for 6 hours to rebuild a data base. with no other evidence, your new carrier is 100 per cent at fault. to avoid this problem i install new pri's, test then retest then have the did's rerouted in the dax then test and use for a week then take the old t's out. the cost is nothing compared to some systems being down for ? hours. i've seen it take days. not a pretty site.
john poole
bellsouth business
columbia,sc
- Thread starter
- #3
your synopsis was correct. Office B dials ten digits (NPA, NXX-1234) to reach office A, but it's a local call nevertheless. After new PRI was installed, office B suddenly cannot call office A anymore, but all our other office CAN still dial office A (but for every other office it's a long-distance call). I am thinking that new carrier misprogrammed the NXX for office A in new T1. My main issue is new carrier saying AT&T's at fault for not releasing the DIDs. But like I said before, if that was the case, how come the other offices could still dial?
no the problem is not with at&t, they do not control did numbers ever. local operating company route did's to a requested pipeline, if a single call from anywhere works, that software is no longer suspect. the co see the digitis and knows where to send them. if the did's were not released by the carrier, they would either go to our old pipe line all the time or receive a fast (120) busy ALL the time. in the voice world, cheaper is not always better. in the data world it's cheaper to use a hub then a switch, it's even cheaper to just splice all your cat fives together, but not always the best idea. even though it will work after you get it right. the carrier does not want to admit a mistake because of possible loss of rev claims. i can start a ld company tomorrow, don't need equiptment just buy bandwidth and resale it. if something breaks i don't have hundreds of people with 20+ years of experience to bail me out. all i can do is make phone calls and point fingers.. i am lucky in a way, with 37 years in telecommunications i don't let to many vendors get by with that type of service. but then i give that type of service either
john poole
bellsouth business
columbia,sc
john poole
bellsouth business
columbia,sc
- Thread starter
- #5
- Thread starter
- #7
- Status
Similar threads
- Locked
- Question
