Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MCD 5.0 Clustered Pickup group issues

Status
Not open for further replies.

KurpeusLondon

Technical User
Apr 14, 2010
119
GB
Hi guys,

I've a rising issue where, when some members of a pickup group try to pickup a call from "others" members, the line does dead.

The setup is the following: A cluster of 12 nodes running MCD 5.0 SP1 and using fully meshed IP trunks network. SDS enable.

For the sake of example, one pickup group contains the following members:

extension located on controller A resilient on controller B
extension located on controller C resilient on controller D

If user on controller A try to pick call to members on controller C, the line goes dead
If user on controller C try to pick call to members on controller A, the pickup works fine.

Controller A and C are physically located on the same "local" site
Controller B and D are physically located on the same "remote" site

SDS form comparison OK
All members are shown belonging to the pickup group on each controller involved


I checked the resiliency guideline and the configuration seems fine. Any thoughts how can I troubleshoot this further ?

Cheers,




 
Gateways, it's always gateways.

When the call is answered, the call is handed off to the devices to talk directly. I suspect your sets are in a different subnet than your controller and the routing has not been configured for them to talk directly.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Hi kwbMitel,

thanks for your answer.

Yes that would be a good hit in some scenarios but that's not the case here. Controller A and C are on the same subnet so do B and D. It's also a fully converged network that has been deployed for years with no firewall in between. IP phones (affected or not) are on the same subnet which is different of the one the controllers are on. With 5000 users If there was any routing issue, I would know within minutes.

 
Yet, still, I will persist to insist that routing is your issue.

The call setup is fine because that is when the controller is in charge of the routing.

Once the call is answered, the call is handed off peer to peer (phone to phone)

If they are truely on the same network (and VLAN?) then they will talk directly to each other MAC to MAC (Layer 2). Run tests with phones residing on the same Data switch vs separate data switches.

Don't let your familiarity with the system fool you into overlooking the obvious.

I've heard the "If there was any routing issue, I would know within minutes" too many times to count. It's always a routing/config issue in the network. Yes - ALWAYS.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Do other network features work?
Any resiliency between the two controllers, specifically A on to C?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top