multisite configuration problems

[manu]

Hi,

I'm trying to implement a multisite configuration and I've got some problems.

I followed every step of Multisite configuration chapter in the deployement guide but there is something I probably do wrong. I looked on this forum but I found no mistake in my configuration.

My problem is that when I try to pass a call between my 2 Tserver, the call leave from the first Tserver, but it never arrive on the second Tserver.

Anyone have a idea?

Thanks,

Manu

[René]

Hi manu,

The multisite configuration is always a bit tricky . Could you post more information about your environment:
- type of PBX
- version of TServer
- type of used ISCC
- is the ISCC communication between the TServers "established"?

R.

[manu]

Ok,

I forgot to precise that I'm trying to implement this on a test environment first. 

PBX : Avaya Defenity ECS
version of TServer : 6.5.306.01
Type of used ISCC : ?? I don't know, where can I found that?
the ISCC communication between the TServers is effective

In the log of the first TServer, I see this event:
Message RequestRouteCall
message EventRouteUsed

Is this normal? What this messages are for?

Thanks,
Manu

[René]

Ok. I will provide you with few hints right now and try to post more information later (my head doesn't work as it should  so I need to check my notes...)

ISCC (Inter Server Call Control) - is the application protocol used by TServer to communicate each other in multisite-configuration. If you don't see the events like EventRemoteConnectionSuccess or EventAnswerAccessNumber etc. and the messages containing the string "ISCC" that ISCC doesn't work = no attached data will be transferred with the call when routed to remote site.

Check the following:
1/ It's possible to make a call between the sites (call from switch A to switch B and vice versa)
2/ At least one Access Code (CME - Resources/Switches/<...your switch name...>/Properties/tab Access Codes) exists in switch configuration and the options "Code", "Target Type" and "Route Type" are configured correctly (Code - prefix used to call remote switch - if any, Target Type should be "Target ISCC", Route Type - check documentation)
3/ There is at least one External Routing Point defined for the switch in Genesys configuration and that ExtRP corresponds to existing Routing Point (VDN with adjunct-route) on switch side.

Steps 2 and 3 have to be applied to both switches


If you can access Genesys Technical Support site or Genesys Documentation CD then I would suggest you to check documentation for TServer for Avaya version 7.0 or higher. The multisite configuration is described there better then in the documentation for TServer 6.5.

René

[manu]

Thanks for taking time for me 

For ISCC, it's seems to work, I see this in TServer log:
message ISCCRequestAuthorize
message ISCCEventAuthorizeResponse
message ISCCEventLinkConnected

But I don't find the events you mentionned : EventRemoteConnectionSuccess and EventAnswerAccessNumber are not in log!  is it normal

I check, the access code exists and the options are configured correctly.

There is a External Routing Point defined on each switch, but I don't understand when you wrote that ExtRP corresponds to Existing Routing Point
When I define the ExtRP, I fill in the Access number, is it what you mean?

To be clear:
On my switch A:
- ExtRP : 6650
- Origination switch : switch B
- Access number : 8006650

On my switch B:
- ExtRP : 7750
- Origination switch : switch A
- Access number : 8007750

Thanks again, 

Manu

[René]

If you don't see the mentioned events (EventRemoteConnectionSuccess...) but there are other events related to ISCC then it should be ok.

"ExtRP corresponds to Existing Routing Point" - I meant that the object (VDN with adjunct-route) with the same number exists on switch side e.g. ExtRP 6650 - VDN 6650 exists on switch.

How are you trying to test the multisite configuration? Please don't forget that ISCC/multisite does work only for the calls being routed between the site by TServer or URS. It doesn't work e.g. in case you're calling using softphone from switch A to switch B.

It could be helpful if you can post here the logs of TServers with a sample call.

René

[victor]

Hi,

just really basic things:

1. let's check if PBXs are connected and can communicate to each other using that VDN
2. check CME settings


(1) - dial the access code you have place for the second PBX plus ERPfrom the phone of the first PBX and then look at TServer log for the second PBX. You should have callOffered, EventQueued, EvenRouteRequest with ThisDN equal to ERP on the second PBX.

If you have this, then we know that it is working. If you do not have it, it means that your PBX is not setup correctly or you have the wrong accesscode-dn.

(2) CME settings sometimes can be a pain in a rear end, but overall you should be able to get it working in no time.
The important things you have to take into account are:

1. create an external routing point fopr BOTH T-Servers
2. under Switch->Access Codes, add the other PBX and add the access code (which is usually accesscode)
3. repeat the same thing for the other Switch (add access code and ERP for Switch A to Switch B)
4. make sure that TServer A has TServer B as a connection and TSErver B has Tserver A as a connection
5. make sure that server-id option TServer A and TServer B is different (set it to 101 and 102 for example)
6. to make it easier to debug make sure that you have this for log-trace-flag in TServer options:
+iscc +cfg$dn -cfgserv +passwd +udata -devlink -sw -req -callops -conn -client +asai_dump
7. match-calls-by inis usually set to "UUI" for Avaya

Here are some screenshots of how my sample switches are connected in CME:

I have two switches : F** and O** (ignore the ***)

Here is the screenshot of how F** witch is connected to O** switch:
[attachimg=1][attachimg=2]
[attachimg=3][attachimg=4]

Do you have it set up like this?
If you could post us the log it would make it really much easier

Best regards,
Vic

[manu]

Hi,

First of all, thanks for the help!! 

So after many test of different settings, I manage to pass a call by dialing the access code + ERP.
It seems I had not properly configured some settings. 

Now I can consider that the communication between TServer works, that's rigth?
Because I try to route a call using a strategy but it doesn't work, I guess there is a problem in my strategy...

Thanks,

Manu

[S]

I believe, you need to set the Route type too, as "Route" / DnisPooling... depending upon ur requirements. Did you check that?

[victor]

[quote author=manu link=topic=2170.msg7702#msg7702 date=1176383466]
Hi,

First of all, thanks for the help!! 

So after many test of different settings, I manage to pass a call by dialing the access code + ERP.
It seems I had not properly configured some settings. 

Now I can consider that the communication between TServer works, that's rigth?
Because I try to route a call using a strategy but it doesn't work, I guess there is a problem in my strategy...

Thanks,

Manu
[/quote]

Oh my gosh,

I missed this thread completely. Sorry about this!!!
The best way to go about this would be for you to post a lof of TServer A and TServer B and URS when you were trying to root the call from A to B.

Now that you can do AccessCode+ERP call go through manually, it is probably something silly - looking at the logs would fix it in in jiffy.

Vic