Has anyone performed an dual integration with a Nortel M1 system. The Unity will be centrally located .local users have 4 digit extensions and the remote users have a 7 digit (location code plus 4 digit extension) the PBX link box can be set up for 4 to 8 digit extension when we set up the link box for 4 digits local MWI works fine when link box is set up for 7 digits we can not light local MWI .any help will be appricated Unity 4.0
This is what we received from Cisco TAC and it fixed our problem...
Symptom: MWI fails for variable length extensions with SMDI serial integration of Unity.
Conditions: If extension length is configured to be the length of the longest extension then zeros pad the shorter extension lengths and extensions are not recognised by the PBX. If DoNotStripZero=NO is configured then Calling Number also has zeros stripped and this causes other issues.
To Implement the Fix:
The .avd file needs to be edited to add the 'V' switch.
For example, using the outgoing lampext entry from \\commserver\IntLib\AVSMDI.avd:
$LAMPEXT= 10 ZR, LAMPEXT
The 'V' would need to be added instead of the 'ZR' entry:
$LAMPEXT= 10 V, LAMPEXT
Once the setting is saved to the .avd file, Unity will need to be restarted for the setting to take effect.
On the PBXLink set the \Configuration\PBX Options\Extension Length value to the longest length extension. For example, if you have both 4-digit and 7- digit extensions, set the Extension Length to 7.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...