SCCS Networking

[picklemogg]

Hello- someone please help. Here is my deal. We have recently installed 1 NCC and have 6 SCCS sites networked together. 3 are in production and 3 are still in testing phase, soon to be added. Anyway all are 5.0 and have latest peps applied. 5 of 6 sites are working just fine. The last site I am having problems with. This problematic site has voice ties to 2 other centers. When I try to network a call in to this site over either route, the call is successfully answered. However, rather than being answered as a skillset call it is being answered as an ACD call. The network CDN is acquired so it isn't defaulting from that level. I just don't get it. Keep in mind that I have configured all other sites in NCC, SCCS, and PBXs and 5 of 6 sites work fine. I have stared and compared SCCS communication parameters, RDBs, etc. Again- I queue a call to a net skillset and the agent at the problematic network site is reserved for the network call. The call is delievered over ISDN to that agent. When the call gets there though it is not answered as a net skillset call, but an ACD call. This has to be a freak thing. Any help would be greatly appreciated. Thanks.

 

[Techfalcon]

hi

I found the networking and planning guides good for this. however you do not have to remove the elan this is still supported in CC6

sccsman

 

[Milesprower]

I suspect the trunking/NACD configuration. Networking issues can be extremely frustrating. It sounds like the symposium servers are communicating properly, but the physical voice connection (performed by the switches) is defaulting.

Check all the switch and trunk configuration, including patches.
I'm not expert on switch trunking and NACD configuration, so I cannot help you there. Maybe someone else can assist in this area.

 

[sandyml]

You might find the following useful:

Title: HLOC not defined on the switch used with SCCS
-----------------------------------------------------------------------
Background:
HLOC (Home Location Code) is used to distinguish between different switches (i.e. M1 and Succession 1000) on the network. Each switch on the network has unique call IDs. If the calls are networked between the switches (either through M1 or SCCS networking), the call IDs on the originating and terminating switch must be set apart by defining a unique HLOC on each switch. This guarantees call ID uniqueness for all calls in the system.
If HLOC is not defined on the switches that send calls to SCCS (either by being directly connected to SCCS or by networking calls to a switch connected to SCCS), any of the following can occur:
1. Phantom calls
2. Agents reported in incorrect state on RTDs
3. Incorrect historical statistics for both calls and agents
4. Calls defaulting
Cause :
Because HLOC is not defined, it is possible that a new call arriving from another switch/SCCS will end up having the same call ID as a call that already exists in the system. This confusion would lead to the discarding of relevant messages in SCCS, eventually resulting in problems with the call (e.g. phantom calls, incorrect RTD information, incorrect historical statistics etc.)
Analysis:
as per recommendations
Recommendations:
The solution to this problem is to define HLOC value on each switch in the network that submits calls to the SCCS server (either through SCCS networking or transferring/forwarding to another switch that is attached to an SCCS server).
If a customer is using an alternative dialing plan to HLOC, it is not necessary for them to make any modifications to the existing dialing plan, but instead simply define a unique HLOC value on each switch in the network (using Customer Data Block, LD 15 NET_DATA).
For more information on the implementation of HLOC, please consult relevant M1 NTPs.
Required Actions:
as per recommendations