sundance-communications.com/forum Forums Active Threads

First, disable the Windows firewall on your laptop, then try to download the default.dat file from the the SD card through eManager

Sometimes I would run a backup thorugh a phone instead of the laptop. That would rule out issues with your eManager. If it fails then it could be the SD card or the card slot on the processor. I think the maximum size that can be used for the SD card is 1 GB.

Hi all,

I’m working with an NEC SV9100 connected to a Grandstream UCM via SIP trunk. Extension-to-extension dialing between the systems works fine. The SIP trunks are set to DDI type, nec side

Now I want to go a step further:
I’d like extensions on the Grandstream UCM to be able to dial external numbers using the PRI trunk connected to the SV9100. Essentially, the UCM will send the call via SIP to the SV9100, and the SV9100 will route it out through its PRI trunk, with no other user interaction.
Has anyone set up something similar?
How should I program the incoming call on sv9100 to achieve this?

Thanks in advance!

I would remove the SD card and put it in a laptop and see there are other files on the card. If there are move them to a safe folder and format the card. Put the card back in the CIX and force format and try backup again.

Hello, Hope everyone of you had a great Easter weekend. We have had this Toshiba CIX100 for years and today was the first time I ran a backup and it failed. I have no Idea why. I rebooted the system and tried the backup again and it failed. I'm worried because I format the SD card before I do a fresh backup so if something happens and it needs to restore there wort be a backup to restore. Any help would be greatly appreciated. Thanks

HI JBean,,, the phones all work ,, No DND on. The solid led is Intercom 1 button. I believe i probably caused this because i didn't have the same version of Avaya manager on my laptop,,,the version on the control unit is higher. Thks

The flashing BLF keys usually indicate the phone at that extension is disconnected. If pressing doesn't work, but direct dialing does, check your BLF keymapping for the receptionist extension. It could have the wrong extension number assigned.The solid lit BLF could mean DND is set at that extension.

Also, you could be on a page other than 'home' page on the phone.

HI As maentioned above i rebooted , and did not help . 4 BLF's Flashing red ,,can't be used as DSS buttons u have to hit intercom and dial ext. # for it worked Intercom 1 stays red all the time. Not sure it is a conflict with the programming i did. ? ...... The phones digit 9508 reception has the DSS/BLF Module. ,,,,,Thks . for any tips.

The only caution is that you make sure the 350x series phone is listed. Searching for NO616, in manualzz.com, the 3500 series phones are not listed.

Carl

Ha, fair enough. Here you go:

Current KSU: 616
Current phones: at least seven 3508, most -035M variety, one -935M (might be one 3503 in there?)
Test phone bought before realizing our KSU is not an 0616X: 6614 (I just found out this morning that while I bought a 6414 off ebay, I was actually sent a 6614 - so that whole experiment was a complete fail on several levels).
Ad-ons: nothing - no clock, music, etc.
Also just this morning found a pair of what look to be new 6620 phones in a storage closet. I'm thinking the guy who left a few years ago that used to deal with this stuff maybe bought them to try out?

Looks like I'm leaning towards just getting a cheap NO616 off ebay. So far, seems to require the least amount of physical rewiring and programming, uses the same J1 and J2 plugs, seems most of the station wiring in the J1 plug matches up, and seems to be compatible with the 35xx, 64xx and 66xx phones. Thoughts?

TIMEOUT!!!

Here's a homework question. HOW MANY PHONES and what type are they? I'm afraid if the Comdial has XE in the part number, it's "a specially designed phone system for type 67xx phones". The 6414L works on an XE system, but the 3508's or 03's probably don't. Now, a 3508 style phone is probably $70 to $90 each. I'd be sad if you bought an NO616 based on a recommendation that "some guy on the internet" gave you without asking what phones you actually have!

Carl

Yeah, I figured as much for option 1. The breaking line buttons were what prompted this whole odyssey to begin with. A few years ago I repaired a few of our 35xx phones (using epoxy) but had to literally permanently epoxy the button PCB into the phone case. Now that the button contacts are starting to fail, the phones are gradually becoming permanently unusable.

Quick question on the NO616 compatibility, the single compatibility chart I found in all my searching lists the 6414 and 6414S as compatible with the NO616, but says the 6414L is not compatible. What's the difference??

1. Buy a tube of lipstick for the pig. A pair of 350X phones have to be pricey and way more expensive than an NO616. Early 350X phones, IIRC actually needed a tube of superglue to keep the line buttons from falling into the phone, but that's another story. If you already bought the 64XX series phones, then you probably need to use option 2.

2. Of course you would have to program the system. For your 9 or so phones, that can't be too difficult. The button mapping commands differ with the models as XE or NO series, but they are fairly easy to grasp the concept. As far as plug compatibility, the first cable in the 616's are usually numbered 10-19 which makes the first 10 extensions exactly the same; you don't have a clock or printer cable in a 616 nothing. You do have to find 4 conductor modular plugs because the lines use RJ-14 (or RJ-25) instead of RJ-11 jacks on the 616.

3. It comes down to what you have or don't have with your current system. The 616 replacement route can run you $40-250. You have all the phones you need, you have no system clock, maybe, and you have no caller ID display to the phone. The DX-80 swap that Ed (EV) bashes, is not a difficult system to wire..remember you're only talking 8-10 phones. That's 2 wire modular jacks on the bottom of the card(s), using the center pins...basic wiring with a modular crimp tool available at any Home Depot/Lowes/Mennards. A shout out to Ed, the Comdial Impact series phones were American made and sturdy, more so than the 3503 and 3508's. The Comdial DX-80 series phones and system were made somewhere overseas, like Singapore or Thailand or Korea. I thought the quality was similar to the 3503's.

I'm sure someone on this board will have some different ideas about phone system prices. If I needed a phone system in a hurry, I'd pick option 2 because I don't have to learn anything new and I own 100% of the phones.

Personally, if my Panasonic dies, I'll just grab another one from the warehouse or actually fire up my IP Phone system. Pretty easy to do in a one-man 2 phone 4 line office.

Carl

Sorry for disappearing for a few weeks. Been (figuratively) putting out fires constantly for weeks on end. I keep thinking, one of these days I'll be able to just come in to work and work on a normal project. One of these days....

My apologies for using the wrong terminology - yes, I meant the entire phones. I promise to do better! In my line of work, the common misnomers are references to vertical load bearing members as "beams" and that appliance in the basement as a "hot water heater".

Back on topic! So my next question is, since it seems pretty certain now that we just have a plain old 616 KSU, which is the recommended route?

1) keep the 616, and track down replacement 35xx phones - PRO: would work without much extra fiddling, CON: old, rare, expensive, maybe will break again in the same way as our current ones?

2) swap the 616 KSU with a NO616 or 616X - PRO: can use newer 6414 phones and possibly others, CON: will I have to reprogram the new KSU and/or all of the new phones? Is it especially awful to do so? Or would the KSU be plug and play?

3) abandon these altogether and move to an entirely different/newer system. Since you said the DX-80 is not an easy swap (what in particular is difficult about it?), and is not great quality, what IS a good option in the myriad of secondhand systems available on eBay and the broader interwebs?

I covet any advice you all can offer. Thanks again!

Don't get me started on, "I need a new line." 🤣

I don't like when phones are referred to as handsets! I'll ask customers to elaborate and I'll explain the difference.

You would have to subscribe here: https://sundance-communications.com/forum/ubbthreads.php/ubb/subscription/id/16

Then download the files here: https://sundance-communications.com...elephone-system-pdf-downloadable-manuals

did you find solution

Here's a friendly tip: Before you reply to a post, CHECK THE DATE! My calendar says it 2025. Replying to a post or reaching out to a member who has not posted or been seen in 5-10 years is going nowhere.

It's also hard to believe you have the "exact same problem" on a phone system that has been discontinued for 6 years. Where were you 6 years ago?

Anyway, a while back ago, we had a discussion about rules, but decided to just keep the board open to older posts. I checked 'November's links and they are broken. It probably means they are no longer around. Since our post traffic is so small, we can see and/or respond to any post. I try to help whenever possible, but I am not your library and software supply company. You might try making a new post, listing what you have done and why you're trying to interface an SL-1100 or 8100 family to asterisk and what you have tried to solve your problem. Then someone might have answers.

Just my two cents....

Carl

Dear November I have the same problem can you send the files please [email protected]

Can you please send the documentation for this scenario i have the same exact situation
[email protected]

i cannot access

Are you positive the issue isn't coming from the trunk side? You'd probably want to do a packet capture to be sure...

I have an SV8100 with 70 IP phones. Connected on a vlan.
It has been working perfectly for years until a few weeks back.

When on a call, you can hear fast beeping and sometimes the call goes silent for a second.

I have disabled the RTP Alarm on the phones which eliminated the beeping but the 1 second silence is still happening.
I have enabled peer to peer in 10-26-01.

Which helped a little but still a problem.
Nothing on the network has changed to my knowledge.

Any ideas?

Thanks for the suggestions. When I retired, I gave them all my spare Samsung stuff, my wife didn't want me to continue to tinker. Now here I am, I will be going there on their spring break to look at it and paging.
I installed a few Avaya I.P. Offices in the past the concern they have is life expectancy now that N.E.C. pulled the plug on the U.S. market entirely who is next?.

Folks, in spirit of what EV607797 said, I've come back to make sure whoever crazy enough to operate those things in production and, by any chance got same parts as I did, gets the most accurate information.

I think I'm now pretty much sure this unit is indeed `-1`. After perusing the menus via PT, it's clear it doesn't have those features I mentioned before, just what's expected from a -1.

It also got 320 KB of RAM (64 KB on the motherboard, plus 256KB over two CXK581000AP-10LL modules at the ROM card.) As for the CPU, it's a TMP68301AF-12 model. As per the datasheet, it's a family of processors that can do 8 to 16 MHz. I think that one may be capable of 12 or 16 MHz, but the oscillator crystal inscription seems to suggest we're doing 8. But I'll never know for sure, since I couldn't find schematics for this KSU, neither 8.1AKSS6KT returned anything meaningful on Google. On KX-TD1232CE service manual, it's indeed a 8.19 MHz (cf. attachments), so I'm again going to assume it might as well be true for 816 as well.

At any rate, though, it is what it is. A very old -1 unit, running 1996 ROM and, therefore, miles away from being able to benefit from latest ROM releases. All I can say is: if you got this unit, stay away from KX-TD193DX or be prepared to get your hands dirty to bodge something.

Now I rest.

Thanks!