Does the U1911 functioning as a trunk gateway support the ringback tone service

If the trunk function is not used, change the dialup timer value of the AT0 trunk to 0. The AR does not need to spend 5s on detecting the ringback tone. A user needs to wait for only 3s to hear the ringback tone. Run the pbx number-parameter 40 0 command in the voice view to set parameter 40 to 0. NOTE: The modification may cause failures of calls transferred through trunks. The pbx number-parameter 40 0 command can be used only when POTS or SIP phones make outgoing calls through AT0 trunks.

All U1900 series unified gateways support SIP/SS7/PRA/R2/QSIG Trunk. U1910/U1911/U1930/U1960/U1981 also support AT0 Trunk, U1980 doesn't support AT0 Trunk. U1911/U1960/U1981 support BRI Trunk, while U910/U1930/U1980 doesn't support BRI.

Monitoring is not supported in U1900.

The U1900 series unified gateway mainly supports two types of services: basic services and supplementary services. - The basic services include intra-office calls, narrowband inter-office calls, and broadband inter-office calls. - The supplementary services supplement basic call services, including calling line identification presentation (CLIP), call forwarding, call transfer, call hold, call park, call waiting, three-way calling, conference call, and outgoing call barring (OCB) services. For more details, see the Feature Guide of the U1900 product documentation.

If the trunk bearer is configured and the ringback tone from the carrier side cannot be heard, check the system settings and set the peerringback parameter to yes. config modify tgld callsourceno <0-255> officeno <0-254> protocol prefix [peerringback] peerringback indicates whether to receive the ringback tone from the peer end. Receiving the RBT from the peer office is a fixed setting for the R2 trunk.