sundance-communications.com/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems Transferring network calls

Let me think about this one. I have an idea though I want to try it first. I've done things that Samsung said couldn't be done so don't think that your out of luck yet. I'll post when I get it to work.

i agree with benb, i have figured out some things as well on systems that they said wouldn't work. maybe we will figure this out and learn something new

Here's another problem I discovered today with their networking... grrr!

We use the networking to save on long distance since each system is located in a different lata.

So we have LCR setup to route calls through the switch that would provide local calling. I have had a couple of complaints where calls would get droppped from time to time.

Turns out since networking is considered to be a trunk call any call made between one switch to another to a trunk starts the co-co timer.

So with the default 20 min timer after 20 mins a call would get dropped. Even worse, from a broadcast standpoint, the timer can only be set for 1 - 250min.

So if we want to do a 5 hour broadcast we have to redial at some point to reset the counter....

Wow dude you just solved my problem!

We have two systems networked together and System B makes all it's calls through System A's phone lines. Well we have been hassling with them getting cut off for a while now and I think you jsut solved our problem. Thank you thank you thank you!

Glad to have helped, you know this really is a great forum. I reset the co-co counter in each switch to 250min, I guess time will tell if there are any ill effects.

One other issue we had when we were running 100R1 to 500R2, after a short period, I want to say 30 seconds or so the audio would go away in one direction.

There is a timer (I'm drawing a blank now as to which one) which basically optimizes the call routing. I guess the scenario would be outside call originates to trunk on system a, but VM is on sys b, but caller needs extension on sys a. After the call is transferred it might be routing the call through sys b, so this timer would check the routing of the call and release the uneccesary trunks. The problem was it would drop 1/2 the call even when the trunk was necessary.

I'm not sure if it was a bug in 100R1 software but we set the timer to 0 and had no more problems, we never tried setting it back to it's default after upgrading to 100R2 software.

You said that the systems were networked? If they are via IP how would a NS key work to stop the barge issue? Probabally will still be seen as a internal call but at least you would see the person's status. If you went all IP on the network calls instead of standard would that bypass any of the issues of time length? Just wondering out loud...

what happens if you only have 1 call key, does that stop the barge in on the conversation

I dont think the problem is that the caller is barging into a call already in progress. The problem is that when the receptionist answers and transfers it to the persons extension across the network it doesn't ring the phone like it would internally. It just goes straight to the speakerphone because between the network all calls are treated as internal. Get what I'm saying?

Ok, I've been thinking about this one and Unfortunatley it's one of those cases where the way it is designed is not going to do what you want it to do. I agree, trunk calls passed over a IP network to another node should still be considered trunk calls and not intercom calls. I have thought about different ways to prevent the call from being dropped on speaker phone though none of it is seemless (like it should be). I think this is something that we should get to the engineers to put into on a new release of software.

I agree with benb. I think that I would press the letter from the 26th. I have talked to Deo before and he seemed ok but he might only be able to do so much. Like a lot of things $$$ dirves their world also. This might need the marketing people to push your issue. Push hard and squeek loudly! Seems like they could disable the speaker if the set is in a busy state