Search results for query: *

Thanks 3racefan3 In the 9500 - ASYD Index 186 Bit 0 = 1 In the 9100 - 50-06-01 = 1 (this is default so should be there) Both are flagged. I unchecked 50-06-1 but got the same garbage until I answered the call.

If this is the issue I think it is, If the call comes in to the SV9500, is routed to the SV9100 station over IP CCIS and the SV9100 station call forwards back to the SV9500 the SV9500 station sees garbage characters where the caller ID should be while the call is ringing. After the 9500 station...

Try running LCPNCL for all routes. If you are controlling outbound Caller ID, it's probably being done with ACPNCL.

I was working on a 9500 not long ago and I was dissapointed to find out it's no longer supported. Came in handy to find our what previous tech's did. DMBL CM0-03 Business, Hotel DMBL Display of Make Busy LENS Data 1. Floppy Disk Name: CM0-03 2. Function This command is used to print out LENS...

I was surprised to find DMBS in the ICS command manual. I don't know when that command was dropped but may have worked on R-11?

Try DMBL or DMBS.

Yeah, if ASPA is not in for Hooking then that will happen.

Check ASPA(L,N) for the extension number and flagged for Hooking. Normal will allow a station to be called. Hooking allows a station to be transferred to.

I'm not clear on the issue but when I see "transfer" I think maybe the extension you're trying to transfer may not be flagged in ASPA(L,N) for "Hooking". That will keep you from transferring that caller.

We chased intermittent talk path failure associated with constant "IP Collisions" in the error log for a long time. We pinned it down to the quad zero IP address issue and used DIM to pull an ARP cache list. It showed a MAC address and IP address 0.0.0.0. I went to our IT guys and told them to...

When we were experiencing intermittent talk path failure on our 9100's the System Alarms were showing 2 "IP Collisions" per minute. They weren't actual IP collisions but were caused by a Cisco device doing some sort of probing that involved an IP address of 0.0.0.0. The 9100 does NOT like...

Did you check "System Alarms". There are some IP issues I've dealt with.

Try running LLEN for 021020 thru 021037 and make sure only stations are programmed on it.

Try ACLN. If it's a fusion system then use the logical route for route number.

To use ANSI.SYS under DOS, a line is added to the CONFIG.SYS (or CONFIG.NT under Windows NT based versions of Windows) file that reads: DEVICE=drive:\path\ANSI.SYS options If this isn't in your config.sys then you will see garbage when you open the old MAT commands. But yeah, this is...

https://files.engineering.com/getfile.aspx?folder=d4d65ce1-7e40-4ef7-9e7e-13b8776e24e1&file=PCPro_SV8100v10.00.zip

That was SERIOUSLY weird!

http://files.engineering.com/getfile.aspx?folder=7be96cc8-91ba-4aa9-875e-f39614bacee2&file=IP_Collision.docx Hey Ebeau97, take a look at the link.

The closest that I've come is to use DIM to pull the arp cache from the 8100. Apparently this box doesn't like seeing quad zero's for an IP address and Cisco Discovery Protocol generates that somehow. The one in red belongs to Cisco. I showed it to our network administrator and he said "your...

Have you looked at System Alarms? We're dealing with an issue involving constant "IP Collisions". Once in a while it overwhelms the DSP's (we think) and there is no talk path for about 5 minutes then it rights itself. Something to do with Cisco Discovery Protocol.