You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Behind most platforms, when the user place the call on-hold, the device sends an invite with the "send-only" attribute. (Which is fully inline with RFC3264)

Some platforms prefer the hold signalling not using "send-only" but "inactive", this can be changed via Auto-provisioning.


Provisioning parameters

Enable "inactive"

BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_1=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_2=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_3=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_4=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_5=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_6=0x1

BS_IP_Data3.ucB_SEND_ONLY_WITHOUT_RTP=0x0

Enable "send-only" (Default setting)

BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_1=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_2=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_3=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_4=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_5=0x1
BS_IP_Data1.ucB_HOLD_WITHOUT_RTP_6=0x1

BS_IP_Data3.ucB_SEND_ONLY_WITHOUT_RTP=0x1



  • No labels