Design and Deployment Checklist
46 Avaya Video Telephony Solution Networking Guide
SIP Limitations
Question 1: In a mixed H.323/SIP environment, are all H.323 MCUs the
supported RMX platform?
Verify that all H.323 bridges accessible to SIP video users are not MGCs.
Yes.
No. SIP video users will not receive video when dialing into an H.323 MGC. Upgrading to the
Polycom RMX bridge will enable video for SIP users.
Question 2: Is the video routing feature set to prefer only H.323 trunks and
not use SIP trunks with a multimedia bearer capability?
Verify that all route patterns containing SIP video trunks do not rely on the multimedia
bearer capability being set.
Yes.
No. Multimedia bearer capability is not set for SIP video calls. As a result, SIP video calls will
route as audio only.
Question 3: Is priority video enabled on a SIP signaling group, and is the
bandwidth allocated from the priority pool as expected?
Verify that the signaling groups at either end of the SIP trunk have priority video enabled if it
desired to use priority bandwidth. Separate sub-domain names may be used to separate
priority and normal users.
Yes.
No. SIP currently has no means to signal a priority video call over a trunk. A system that
receives a call on a priority trunk will always be allocated bandwidth from the priority pool.