intercluster trunk and route-group

[KAROLY KOHEGYI]

Hi The customer have a two sites. The CM clusters work on both side and there are intercluster trunk beetwen them. every side have a exits to PSTN.

We would like some route( number) have a alternative path towards the other site if own PSTN is failed.

Our problem :

We can not insert the intercluster trunk ( device ) in the route-group. Any idea ?

[paul.harrison]

Insert the intercluster trunk into another route group.

Then add both groups to a route list.

Then point your outgoing calls (route patterns) at the route list and NOT the gateway.

Just make sure that the calling search spaces applied at each site have the correct partitions to allow the calls over the intercluster trunk to access the far site route patterns.

Paul

[KAROLY KOHEGYI]

Hi! Thanks !

We solve this problem during this time.

The problem was we connected the intercluster device to route-pattern directly. thus the trunk device does not appear in the route-group.

Is it normally ?

We remove all gateways and trunk from route-pattern and use route-list definitions in the route-pattern only.

[paul.harrison]

If you assign a gateway / intercluster trunk, direct to a route pattern then you can't add it to a group, as you discovered. You must remove trunk / gateway from the route pattern config, add it to the route group, the group to the list, and then add the list back to the route pattern.

You can configure the groups and route lists before removing the gateway, that way you can point the route pattern at the list when you remove the gateway that way you have less outage whilst you redo the config.

Good to see you solved it

Paul