Have a customer w/ an old Toshiba PBX that we are changing out w/ a new Avaya IP Office. This customer is serviced by two T1's (not PRI's) provided by CenturyLink. One T1 is for local calling and inbound DID's and the other T1 is for inbound 800 calls and LD toll calls. On the old PBX, no matter which circuit I make an outbound call on, the called party will show this custoemr's name and number on their phone. When I plug these circuits into the new IP Office PBX, any outbound calls show "UNKNOWN" on the name and number.
CenturyLink tells me that because these are T1's and not PRI's, that there is no inbound calling name or number and that outbound calling info from the PBX is not supported either. However I do get calling info from the old PBX, but not the new one. No matter what config I use in the new PBX, I get no calling info to go out.
These T1's go thru an external CSU before going to the old PBX. When I put my new PBX into service, I bypassed the CSU's....as I don't think they would affect any calling info anyways. Both T1's are E&M Wink Start.
Any thoughts on how to remedy this? All I want is for the customer's main number to be displayed on all outgoing calls.
I think that CenturyLink's records are wrong. Can you re-purpose the ports on the IPO to emulate a PRI rather than a dry T1 and see what happens?
T1 circuits aren't smart enough to pass outbound information. My guess is that they really are PRIs.
I could give that a try and see what happens. All of my inbound and outbound calling is working, configured as T1 (E&M Wink Start). If I reconfigure as PRI, I am afraid my call functionality will stop. The local T1 only has 12 channels and the LD T1 has all 24 channels available. I can surely give it a try and see what happens though.
The C/L account reps have repeatedly told me that this customer is on T1 E&M and that to achieve this functionality would require an upgrade to a PRI circuit. They currently do not receive any calling info on the inbound calls on the old PBX, but every outbound call shows their name/number. I would think that if C/L is supplying this, it should show up on every call regardless of the PBX connected to the circuits.
The ports in the C/L switch are assigned to one or more Trunk Group(s). The switch should be able to assign a telephone number to the group(s). I would have C/L verify what is there and correct as needed.
Else, ISDN/PRI will allow you to generate originating ANIs.
I have the C/L account rep contacting repair right now to determine exactly how it is provisioned. Odd how if it is a T1 / wink-start circuit, that calls from the old PBX are displaying name/number on outbound calls. C/L would have to be providing this information, which should also be supplied when the new PBX is in service.
When MCI was in business, one could order a T-1 with inbound ANI and outbound ANI. I had several of these in service at one time. Alas, when MCI went away, the only way the carriers, here, would provide CID was with a PRI.
Rcaman
I just got an email from the account rep that told me CenturyLink was not providing any sort of ANI on the circuit and that it must be coming from the old PBX. Now to figure out how this PBX (which no one knows how to get into) is supplying outgoing ANI on this type of circuit.
What "old" Toshiba is it?
Rcaman
It is a Strata...but I cannot find my note at the moment as to the exact model.
An update on the outgoing ANI: I went back on-site today and found that if I place a local 10-digit call or an outbound 8XX call (which both traverse the local T1) then I get Unknown Name / Number. If I place an outgoing toll call or if I do a 1+ on the local call, the calls then traverse the LD circuit and I do get ANI to show up on the receiving end of the call.
It appears that any call that traverses the LD circuit passes along the correct info, but anything going out the local circuit does not. When I was on-site the other day, I was placing all local calls as 10-digit. I never considered trying to do a 1+ on local calling. If I do a 1+ local number, it works.
Now if I can get C/L to get the local circuit to perform as the other I think I may be good to go.
C/L needs to check the optioning in their Local Service switch.
It could be optioning, but I don't think so. The clue is in the 1+ dialing. Obviously, the LD carrier is providing CID. Maybe you could find out who is handling the LD and see if they can route local 10 digit calls as well if C/L can't do it.
Rcaman
I believe the LD carrier is AT&T. That idea is worth investigating.
I possibly have a related issue.
Four years ago our name changed. I changed everythine I can think of in my old Avaya G3siV11. It still, occasionally comes up with the old name. What I think is happening in my case is that each carrier has a data base (we are served by AT&T) and when a call is made to someone with some fly by night carrier, the carriers data base populates the old name. Not sure this will shed any light on this particular problem.
If a carrier is a reputable company, they will make the changes that reflect throughout the system. Some carriers are really not carriers. They resell service from other real carriers. They are limited to being able to make CID changes to what they actually control, which is normally, not much.
So, as an example, a call is made and the routing selects "Jeb and Billy Bob's down home telephone shed" as a path for your call. They have no CID on their equipment, or if they do, it's relegated to something weird or not correct. The call ends up with missing or goofy CID.
The bottom line is if you want correct CID, you must keep meticulous records and hound your carrier to fix the problem. Armed with enough data and persistence, they will make the appropriate changes just to get you to stop bothering them.
Rcaman