Recent content by phonetech2012

Yes we want them to dial the same way they would dial 911, we just want them to be able to dial 988. I have the DMI deleting 0 and inserting the 9 since it is stripped off for the ac1.

Thanks for the reply. I outed all the nxx entries from 880-889. The I was able to build 88 as a SPN with a DMI inserting the 9, but it is still not working. Built the same as 911 now, but no good.

Hi has anyone been able to set up 988 on their pbx? I can not add the SPN of 88 since we have NXX's as I am sure so does everyone else. I tried acd to phantom out to the 800 number for 988 but fast busy. I think the only way is with SPN 88 set up since 9 is our ac1 to dial out.

Anyone familiar with Xeta? We have no documentation and need to flush the data reports since they are apparently maxed out. Thanks

CCM 6.0 Made a change to a agent key without deacquiring first, clan was down. IT fixed clan by rebooting ccm server, now the agents do not show up when trying to list them. Agents do not acquire or deacquire, grayed out. Real time displays do not populate at all. All agents show deacquired in...

We have a NI2 tie line between avaya ipo and nortel 61c. When the avaya calls over to the nortel, example, avaya dials 81430, the dch messaging shows 81430 being dialed but then it actually is calling 140 on the nortel. This is happening on multiple different extensions, some calls go through...

problem fixed..MPO Data needs to always be dis dis, we had dis atn, so call transfers that failed through the vm channels default to the operator, Now calls will simply disconnect as they should

found the problem..drum roll please...it was the speed call list 0 that had the ac1 code plus 1 programmed on the 1. So every call that came in with the 1 got the default pretranslation treatment. Perfect example of why we do not build anything on speed call list 0

So the 3.1 does not seem to be the issue. I do see that incoming calls that fail are basically making 3 calls at once. We are using loop 44, so channels 44-1, 44-2,and then 44-1 are being used for the single call in to a 1xxx extension. I guess this is why we are getting the dch error cause 42...

Found that the calls that fail are coming in as 3.1 khz audio {BCAP 85} and the calls that are good come in as speech {BCAP 81}. So it's getting kicked back to Verizon. We'll see

Thanks for the files again. Unfortunately for me I've been trying to get the dnb file from the remote pc to my pc all day, and finally got it over to find that the excel file is locked and I cant enable editing to upload the dnb. My laptop is always a piece of shit so I am sure thats the...

Thanks again. I tried the file but dont see the .exe file only see .txt Ill check again. Do you think this could be corrupt data? The software has not changed in many years. I am thinking of doing a sysload.

Verizon tested and was able to get a call into their Tberd so the problem looks like its on the PBX side for sure. I just outed all the PRI data and rebuilt it, but still same problem. Where is there a 1 conflicting on this pbx? I checked FCR in 49 and it has a bunch of deny's that all start...

I tested all this with a new IDC table. Thanks for the script offer but yeah these numbers are all over the place. Still waiting for telco to come to site and get a test call into their Tberd.

Thanks for that. You might be onto something with the digits. I did bring it up to Verizon already, but they came back said they are sending 4 digits. I did however put in 10 digits in the IDC table and the call went through to a 1xxx range. They still deny the issue is on there side. I am not...