Cisco realizes that for many companies migrating to IP communications overnight is not always in their best interest financially or otherwise. Therefore, we understand that until the migration is complete, our customers may have multiple systems from multiple vendors. By documenting how the systems interoperate, our customers will have not only an understanding of what end-user features work between systems, but also a smoother installation and migration process.
What if I cannot find an application note that mirrors my deployment?
If you cannot find your configuration listed in the application notes, here are some tips:
·PBXs or IP PBXs in the same product family should behave similarly. For example:
Nortel: The PBXs in the Nortel Meridian 1 family should have similar results. The Nortel Meridian 1 Option 11C will have similar configurations as the Nortel Meridian 1 Option 61C and Nortel Meridian 1 Option 81C. Note that Nortel's CS2100 and CS1000 are in different product families and will have different results.
Avaya: The PBXs in the Avaya Definity G3 family (versions VSI, R, CSI, and SI) should be similar. The Avaya 8500 is also in the same family as the Avaya 8700 and should also be similar.
Siemens: The PBXs in the Siemens 300 family also should have similar configurations. This family includes the 330, 340, and 370.
·Gateway configurations should be similar if the gateways are Cisco IOS® Software- based with an IP voice image and use the same protocol (Media Gateway Control Protocol [MGCP], H.323, or Session Initiation Protocol [SIP]). For example, a Cisco 2801 Integrated Services Router gateway should have similar configurations and results to the Cisco 3845.
What if I have a different release of a PBX or IP PBX than what Cisco has in its application note?
Different PBX releases have different capabilities. For example, not all PBXs come with QSIG as a default. The PBX may need upgrading to get QSIG and their calling features to interoperate.
On the other hand, typically, if the PBX in our application note is a lower release, the results should be similar to the PBX of a higher release. For example, if caller ID worked on the lower-level release, then caller ID should continue to work on the higher-level release. We work on the assumption that PBX and IP PBX vendors typically do not remove features, but add them as their product evolves.
If I find a problem with my PBX or IP PBX, can Cisco help me get the vendor to fix the problem?
The best and fastest way to solve interoperability problems that deal with another vendor's system is to have the customer, rather than Cisco, engage and work with that vendor to resolve the problem.