No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


How to interpret call logs on scenario where a point-to-point call escalates to a multipoint conference.

Publication Date:  2017-02-11 Views:  185 Downloads:  0
Issue Description

We have 3 endpoints and a standalone MCU that are added to SMC2.0 and registered to the SC.

When a point-to-point call is made, the call logs on endpoint show different H323 numbers than when the point-to-point call escalates to multipoint conference in MCU. Is needed to understand how the new called/calling numbers are formed/concatenated.

SMC2.0/SC  software version: V500R002C00SPC900 

Endpoints (TE30, TE40 & TE50) software version: V500R002C00SPC600

MCU  software version: V500R002C00SPC600


1. In the first phase, Site1 calls Site2. Site1 then calls Site3 and at this point is triggered the multipoint conference. 

The call logs to be explained look like this:

Site1 - TE30 (07558000):

Site2 - TE40 (07558002):

Site3 - TE50 (07556000):

2. To understand what are the numbers, we need to check the following settings on SMC:

SMC web page -> System -> Conference -> Conference ID

SMC webpage -> Devices -> MCU's -> click on the MCU that holds the conference to check its prefix:

3. Check the ongoing conference started at point 1:

SMC webpage -> Conferences - > Scheduled Conference - > click on the ongoing conference - > Conference Details -> Here is found the Conference ID:

4. Check the call list on the MCU when the multipoint conference was started:

SMC webpage - > Devices -> Switch Centers - > click on the SC where the endpoints and the MCU are registered -> click on tab Registered Nodes -> check from the list the MCU and below click on Call list:

5. Conclusions:

 When the point-to-point call escalates to multipoint call (Site1 calls Site3), things happen like this:

I. Site1 will call the conference id, concatenated like this: [unified_access_number]+[MCU_prefix]+[sub-conference_ID_number]

When Site1 sends admision request to call site3, it will receive an admision confirmaton from SC that it needs to call conference ID:


Then the call proceeds:

II. Site2 will also call the same conference id: [unified_access_number]+[MCU_prefix]+[sub-conference_ID_number]

*Comment: On the web interface the call logs of the Site2 indicate that Site2 received a call from 8000075520000. Actually, Site2 receives a Facility message from Site1 asking to call the conference ID. Thus, it is recorded as a receiving call, although is clearly that Site2 calls the conference.



3. MCU will call Site3, using as calling alias: [MCU_prefix]+[sub-conference_ID_number]