Search results for query: *

This was working for 10 years and then suddenly stopped.

I have a 2250 with EES programmed on key 9. I have replaced the 2250, out'd and rebuilt even changed the dlc and still not working. Any suggestions? thanks,

chances are the table is already built so you would do a change instead of new. To see if it already exist use ld 21 to prt clid

I have a script that is currently activated, but would like to log the CLID of every call that hits that script. Could I use the following statement: IF (CLID = @) THEN Route 7724 END IF Then where would I retrieve the CLID's from? Thanks.

They term to the Strata Dialer for the agent talk path. CLID is being passed from the LEC to the PBX, but it is from the PBX to the Strata Dialer that the CLID is not being passed.

I have acquired a 61C running 25.40 that has 2 tie trunks configured as E&M4 that terminate to a Strata Dialer. My problem is that it is not passing CLID for incoming calls here is the configuration of my trunk and route: TN 012 01 TYPE TIE CUST 0 TRK DTI PDCA 1 PCML MU NCOS 5 RTMB 74 1...

change CLS to HTD and FND

I am working on CCM 6.0 and the customer if complaining about a 3 second or 2 ring call delay to ACD phones. Any suggestions to make if less. Have tried to adjust force delay timer in contact center and does not change.

Are the extensions CDP'd from the Nortel? If not they need to be because the Nortel will not know where to send the call to.

I agree with Dasheen. I have changed out a dozen, but it could also be the MSC which I have seen cause the same issue.

Also looking at your programming I would strongly suggest that you use a group hunt instead of using hunt or FDN. When using FDN and you have a bad port the system will not bypass it. If you build it as a hunt group you can add and remove ports with out affecting the group.

Because the Cisco is not smart enough to bypass that trunk. Iwontremember had the best solution. We were in the area before, but did not select the advanced tab. Now we have the channel out of service and it will give us an opportunity to troubleshoot tonight. Thank everyone for the help.

I logged into my cm/service parameters configuration and selected my active server, but do not see channel maintenance. I am on release 4.1

It is a PRI 23 b-channels and 1 d-channel.

I have a PRI between my Nortel PBX and Call Manager 4.1. We have identified a problem with channel 23 on the Call Manager side. Is there a way to busy out the channel on the Call Manger side so that no one tries to access it? Thanks.

SecureCRT is an execellent applications. Support TAPI, RLogin, SSH1 and 2, Telnet and serial.

I am also seeing PRI227 DCH: 27 DATA: 0000000E and PRI227 DCH: 27 DATA: 00000007 messages. I know it means Null state for the DCH, but not sure what messages 7 and E are.

That's what you would think. But I handle the CM and PBX Voice portion and we have not changed anything.

We have an 81C 4.5 with a tie to Cisco CM 4.1 Our network crew has made some changes on the network side and now all of a sudden we are getting BUG4023's on almost every call between the PBX and CM. Here is the bug: BUG4023 BUG4023 : IFC 13 DCH 27 IN PRA OR IPRA BUG4023 + 00AECFC0...

What version of TM are you using? Also are you collecting CDR and or traffic via IP?