Got it

Failed to join a conference by dialing the Ad Hoc number or Unified Access number

Created: Apr 8, 2020 07:24:15Latest reply: Apr 8, 2020 07:26:18 508 1 0 0 0
  HiCoins as reward: 0 (problem unresolved)

Hello, dear!

Have a good day!

When I dial the Ad Hoc number or Unified Access number, I cannot join the conference.

Please help me to check it!

Thanks!

Featured Answers

Recommended answer

Hey,girl
Created Apr 8, 2020 07:26:18

Hi, dear!

Welcome to the community!

The process of dialing an Ad Hoc number or a Unified Access number is as follows:

The SC receives a call > Report the event to the SMC and request the called MCU > The SMC sends a response to the SC and notifies the SC of the MCU alias (SIP URI or H.323 ID) > SC Search for the called party.

So, if the call fails, check the MCU allocated by the SMC to the SC in the response.


  1. View the SMC2.0 system log. You can find the MCU allocated for the IVR call. Assume that the allocated MCU is 5.107_MCU.

  2. In the MCU list, check whether the MCU is registered with the SC to which the calling terminal belongs.

  • If the MCUs are not on the same SC, configure a search rule to specify the SC. The search rule must match the alias of the MCU, that is, SIP URI or H.323 ID, instead of the original ad hoc number or unified access number. 

  • If the MCU is registered with the SC and the SIP URI or H.323 ID (determined based on the calling protocol) of the MCU is displayed in the registration list of the SC, check whether the called number is changed or whether the called number is routed to another device due to a rule.


Best wishes!


View more
  • x
  • convention:

All Answers

Hi, dear!

Welcome to the community!

The process of dialing an Ad Hoc number or a Unified Access number is as follows:

The SC receives a call > Report the event to the SMC and request the called MCU > The SMC sends a response to the SC and notifies the SC of the MCU alias (SIP URI or H.323 ID) > SC Search for the called party.

So, if the call fails, check the MCU allocated by the SMC to the SC in the response.


  1. View the SMC2.0 system log. You can find the MCU allocated for the IVR call. Assume that the allocated MCU is 5.107_MCU.

  2. In the MCU list, check whether the MCU is registered with the SC to which the calling terminal belongs.

  • If the MCUs are not on the same SC, configure a search rule to specify the SC. The search rule must match the alias of the MCU, that is, SIP URI or H.323 ID, instead of the original ad hoc number or unified access number. 

  • If the MCU is registered with the SC and the SIP URI or H.323 ID (determined based on the calling protocol) of the MCU is displayed in the registration list of the SC, check whether the called number is changed or whether the called number is routed to another device due to a rule.


Best wishes!


View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.