Hi,
I have been reading your forums long time ago and I always found some advise here which helped me but this time I haven't found anything about the problem that I am experiencing today with the Mitel cluster which I am responsible for. In a nutshell we have a 28 elements Mitel cluster on MCD5 SP2 PR1 now (Hub IP trunk topology). We have upgraded from 9.0 and OPS Manager sync step by step to the latest firmware (9 -> MCD4 SP4 -> SDS sync -> MCD 5) and always had 2 controllers in the cluster "dedicated" as SIP gateways with SIP trunks to the firm's other region Cisco system which has always worked well. From the other Mitel cluster nodes calls to these regions are routed via Mitel IP Trunks via these Mitel "gateways". All functions like divert, conference, display name (in both ways) were fine but since we have upgraded to MCD5 we have issues with the display name on the Mitel phones when you call a Cisco number but not in all cases! When I have phones directly registered on the "gateways" (the SIP trunk is local) I get back the called party name on the Mitel phone so all fine but when I do the same from an other phone registered on one of the Mitel cluster nodes (cluster routed call to SIP) the name does not pop up if the same extension is called just shows the IP trunk name configures in Trunk Attributes. If they dial me all fine all cases. At first I thought it is some SIP trunk config issue because MCD5 has more options to set but not because I see P-Asserted Identity in the traces sent by the Cisco and works on "locally" registered phones I think this is some Mitel signalling (MiNet) issue. In my lab I have tried to all kind of COS and SIP trunk config variations mostly focused on the Privacy, Display and Trunk fields, also tried with Direct IP trunk and also with the first version of MCD5 and later step by step but did not help so I am out of ideas now. Our Mitel partner asked Mitel but no answer from them yet. I don't know maybe Mitel has changed this feature to "force" you to use MBG as SIP gateway or simply just a bug or missed a setting which causing this? Have you seen this issue?
Thanks
Krisz
I have been reading your forums long time ago and I always found some advise here which helped me but this time I haven't found anything about the problem that I am experiencing today with the Mitel cluster which I am responsible for. In a nutshell we have a 28 elements Mitel cluster on MCD5 SP2 PR1 now (Hub IP trunk topology). We have upgraded from 9.0 and OPS Manager sync step by step to the latest firmware (9 -> MCD4 SP4 -> SDS sync -> MCD 5) and always had 2 controllers in the cluster "dedicated" as SIP gateways with SIP trunks to the firm's other region Cisco system which has always worked well. From the other Mitel cluster nodes calls to these regions are routed via Mitel IP Trunks via these Mitel "gateways". All functions like divert, conference, display name (in both ways) were fine but since we have upgraded to MCD5 we have issues with the display name on the Mitel phones when you call a Cisco number but not in all cases! When I have phones directly registered on the "gateways" (the SIP trunk is local) I get back the called party name on the Mitel phone so all fine but when I do the same from an other phone registered on one of the Mitel cluster nodes (cluster routed call to SIP) the name does not pop up if the same extension is called just shows the IP trunk name configures in Trunk Attributes. If they dial me all fine all cases. At first I thought it is some SIP trunk config issue because MCD5 has more options to set but not because I see P-Asserted Identity in the traces sent by the Cisco and works on "locally" registered phones I think this is some Mitel signalling (MiNet) issue. In my lab I have tried to all kind of COS and SIP trunk config variations mostly focused on the Privacy, Display and Trunk fields, also tried with Direct IP trunk and also with the first version of MCD5 and later step by step but did not help so I am out of ideas now. Our Mitel partner asked Mitel but no answer from them yet. I don't know maybe Mitel has changed this feature to "force" you to use MBG as SIP gateway or simply just a bug or missed a setting which causing this? Have you seen this issue?
Thanks
Krisz
