This is an old revision of the document!


A PCRE internal error occured. This might be caused by a faulty plugin

====== Manage_cidnum ====== <note important> Transport CIDNum requires relay support. </note> When we need to set different CIDNum for different applications, the order in which the system uses the calling numbers is as follows: - Truck CIDNum (Mandatory) - Agent CIDNum (Login status) - Campaign CIDNum (Login status) - Device CIDNum - Truck CIDNum ===== Telephone system ===== * Mandatory use of a unified calling number. CIDNum can be forced on a specify trunk in the system, and all outbound through this trunk ignore any other settings and use this CIDNum. {{:en:how-to:选区_0028.png?750|}} {{:en:how-to:选区_0029.png?750|}} ===== Telephone system ===== * Use a uniform CIDNum, sometmes devices require a separate CIDNum. {{:en:how-to:选区_0030.png?750|}} ===== Own call center ===== * The agent has a separate CIDNum {{:en:how-to:选区_0031.png?750|}} <note tip>When the phone is checkin as a agent device, the system will priority to use the agent CIDNum, otherwise the device CIDNum will be used.</note> ===== Campaign call center ===== * Each campaign has a separate CIDNum. {{:en:how-to:选区_0032.png?750|}}

en/how-to/how_to_manage_callerid_number.1486543137.txt.gz · Last modified: 2017/12/12 03:11 (external edit)
Recent changes RSS feed Debian Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki