132-S-916.2 · Question #181
An IP Office is being networked to an Avaya Media Gateway Server using H.323 trunks with QSIG. Which statement is true?
The correct answer is C. Name and number presentation is supported. See the full explanation below for the reasoning.
Question
An IP Office is being networked to an Avaya Media Gateway Server using H.323 trunks with QSIG. Which statement is true?
Options
- AOnly the G.723 codec is available.
- BSmall Community Networking is supported.
- CName and number presentation is supported.
- DBoth systems must be on the same IP subnet.
How the community answered
(36 responses)- A6% (2)
- B3% (1)
- C81% (29)
- D11% (4)
Community Discussion
8
Ola B.Jan 22, 2026The correct answer is C, name and number presentation is supported. When you tie an IP Office to an Avaya Media Gateway Server over H.323 trunks with QSIG, the QSIG signaling layer is exactly what carries the supplementary service information like calling name and number, so spin up a lab trunk between the two and watch those QSIG messages flow to see it firsthand.
Bao N.May 11, 2026C is the one you want, and it makes sense once you remember what QSIG actually brings to the table. The whole point of running QSIG over H.323 trunks between IP Office and an Avaya Media Gateway Server is to carry supplementary service information alongside the voice path, and name plus number presentation is exactly that kind of supplementary service. QSIG was designed for inter-PBX signaling precisely to pass display names and CLI data across system boundaries, so the two platforms can show a caller's name on the destination phone even when the call crosses the trunk. The other options fall apart quickly: G.723 is not the only codec available on H.323 trunks, Small Community Networking is an IP Office to IP Office feature and does not apply here, and there is no requirement for both systems to share the same subnet since H.323 routes just fine across IP networks.
Samuel O.May 13, 2026Solid breakdown, and worth adding that QSIG over H.323 also handles call-transfer transparency across the trunk, so blind and supervised transfers preserve the original calling party name all the way to the final destination rather than replacing it with the transferring extension.
Anjali D.Feb 12, 2026I kept second-guessing myself on B, but QSIG is literally built for name and number presentation, so C is the one.
Tomasz V.May 31, 2026Thought D was right, but QSIG was literally designed to carry supplementary services like name presentation across PBX boundaries.
Yusuf A.Jan 31, 2026Got C on mine too, QSIG literally exists to carry name/number signaling between PBXs.
Samuel O.May 16, 2026B trips up a lot of people because Small Community Networking sounds like exactly what you are doing when you link two Avaya systems, but SCN is an IP Office to IP Office thing, not what you get over H.323 trunks to a Media Gateway Server. The whole point of specifying QSIG in this scenario is that the supplementary services ride along, and name and number presentation is the classic example, so C is your answer.
Bao N.May 17, 2026SCN trips up so many people on that question, and Samuel nailed the H.323 versus SCN distinction, but the thing that locks in C for me every time is remembering that QSIG was literally built to carry those supplementary service messages across vendor boundaries, which is exactly the scenario they describe.