Hey Guys-

I've recently installed an ESI 200- At one time I was a certified ESI installer, but the company I worked for got out of the phone business, so, every now and again, I install a system. Usually works well, unless there is an issue.

I posted a couple days ago about a system i just installed is having issues with the outgoing caller-id. Everything in the ESI is set correctly, but the CO is still not seeing any outgoing digits.

Does anyone know of a certified dealer in the Kansas City area or Wichita that would like to take over as vendor on record, so ESI can dial in just to make sure everything is covered.

I've verified that the CO requires 10 digits outgoing, and ensured there is a number in section 2-2-5, I'm stummped, and am pretty sure the issue is CO, but can't prove it.

Thanks

Contact one of the Mods....they may have an answer for you.



KC is thin on ESI people.

Thanks KLD- appreciate it- I have the CO combing through their programming one more time, just to see if they come up with anything. If nothing else, I'll take an existing system that works over there and test it out.

I'll call my rep this morning and see what i can get for you. DOn't be afraid to shop them if i get you more than one.

ESI gave me the name of a dealer in Houston to help one of my customers who was opening an office there. I asked for cabling prices and the Houston reseller tried to gouge me. I googled ESI and Houston and found someone else.. who i really liked.

When the first guy called me back i told him i felt they were trying to gouge me .... he backtracked and told me he mistakenly quoted plenum. I told him i figured he heard i was from NY and mistakenly assumed i was from NY city and was used to high prices.... and i wouldnt even consider doing business with someone like that.

PM Sent

' Usually ' The Carrier sends out the Name and Number. It could be a ' mis-match ' type of Signaling You could try a different setting..
F2134 :


Nortel — DMS100

• AT&T/Lucent — 5ESS

• National — NI2 – Default

• Siemens — EWSD

Yeah, I verified it was an NI2. after some more testing, we have determined that the phone system is ONLY sending out digits that are in 2-2-5. So, I can change that, and the CO picks up only that number, not the number in the CID field.
I'm going to test this weekend by taking this system to one of my other customers, and hooking it up to their PRI, and see what number actually goes out- as I know the other customers is going out correctly. And I have gone through each section of each system together, and they match perfectly.

Thanks guys

F225 is for incoming translations only. f31 is the only field you have that will change the carriers default CID. Once the CID field is populated for that ext. in f31 the entered digits will appear with the name as "unavailable" as the CID for outgoing calls on that ext. This is per ext. If the CID field in F31 is blank the carrier will send the CID listed for the PRI. It may appear that the digits entered in f225 are what is being sent but only because that is same number as the main BTN listed with the carrier to send as the CID.

hey sst- in field 31, I have a certain number I would like for the outgoing caller ID. The number that is going out (no matter what ext I try) is going out as the number in 225. If I change the number in 225, the new number I put in there is going out- so, it is not even looking at f31 first, but just going out as the number in 225. I did take the system to a customer that has a PRI that is working the correct way, and same thing- still going out as the number in 225 (and, the number in 225 is different than the primary number of the BTN)

Even on the ext. that have a blank CID field, are going out as the number in 225. And, I probably changed it to 5 or 6 different numbers, and everytime, it went out as the number I changed it to in 225.

I'm at a loss, as everything in the switch appears to be programmed exactly as my other customers, which is working.

Thanks

Well that's not right all, F225 should not be changing the out going CID number. That system sounds pretty whacked. You'll need to update the system software to the latest version and try it again. If the trouble continues after the software update you'll need to get ESI tech support into the system to correct the CID issue. The most current cs200 software is 14.5.44.00
you should be using System Programmer 1.2.14.17 also. Good luck with this one.

I stand corrected. I just looked up F225 in the manual:
F225:..."If the PRI span is used for outgoing calls, pilot table entry 1 is used for outgoing Caller ID, as well. Because of this, pilot number entry 1 should always be programmed with 10 digits....
Note: An extension’s Caller ID number setting (see “Function 31:....Extension definition and routing) overrides the pilot number’s Caller ID information set here."....
F31:...Caller ID — Used for outgoing calls to identify the extension and for callback to the specific extension or another extension nearby. Each entry must be valid and 10 digits in length.
If there is no entry here, the PRI pilot number will display as Caller ID....

This may not help but but worth a try: disable PRI Caller ID Forward in F166. I've had two carriers that this cleared up some outbound issues with.

Resolution: The sw and switch was an outdated bind, we upgraded the whole thing, and it is working now.