Share via


What is the process to get meeting ID

Question

Tuesday, May 10, 2016 6:16 AM

Hi there,

Just analysing one S4B client trace about the meetings. And one question pop up on my mind:

Who is defining the meeting ID when clicking the "Skype Meeting" on the Outlook's calendar?

When I'm looking the client's log in the snooper I can see that the first message which contains the meeting ID is outgoing message from my client to servers (see the red line):

05/10/2016 INFO :: Sending Packet - 10.20.30.40:5061 (From Local Address: 10.11.22.33:52318) 2650 bytes:
05/10/2016 INFO :: SERVICE sip:[email protected];gruu;opaque=app:conf:focusfactory SIP/2.0
Via: SIP/2.0/TLS 10.11.22.33:52318
Max-Forwards: 70
From: <sip:[email protected]>;tag=ce8f1ffa49;epid=1d4efedcc7
To: <sip:[email protected];gruu;opaque=app:conf:focusfactory>
Call-ID: 7ba95a1cb2e34f6b93a04a75fb345afb
CSeq: 1 SERVICE
Contact: <sip:[email protected];opaque=user:epid:OAf4A4tJcV2XXpH3Eiq_KwAA;gruu>
User-Agent: UCCAPI/15.0.4813.1000 OC/15.0.4809.1000 (Skype for Business)
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="54240A57", targetname="sip/LyncFE01.domain.net", crand="09e165bb", cnum="68", response="040400ffffffffff0000000000000000aee5cd40cdb01b0052f2444a"
Content-Type: application/cccp+xml
Content-Length: 1845

- <request  xmlns="urn:ietf:params:xml:ns:cccp"
                mscp="http://schemas.microsoft.com/rtc/2005/08/cccpextensions"
                C3PVersion="1"
                to="sip:[email protected];gruu;opaque=app:conf:focusfactory"
                from="sip:[email protected]"
                requestId="115780796">
    -  <addConference>
        -  <conference-info  ci="urn:ietf:params:xml:ns:conference-info"
                        entity=""
                        msci="http://schemas.microsoft.com/rtc/2005/08/confinfoextensions">
            -  <conference-description>
                   <conference-id>3TJYNCZC</conference-id>
                   <admission-policy>openAuthenticated</admission-policy>
                   <separator  cis="urn:ietf:params:xml:ns:conference-info-separator">
                   <pstn-access>
                   <separator  cis="urn:ietf:params:xml:ns:conference-info-separator">
                   <autopromote>2147483648</autopromote>
                   <pstn-lobby-bypass>true</pstn-lobby-bypass>
                   <server-mode>14</server-mode>
            +  <conference-state>
            +  <conference-view>

I thought it should be the focus factory which is setting up the meeting ID, but have I learnt something wrong? Above looks like the client is defining the meeting ID.

Petri

All replies (6)

Tuesday, May 10, 2016 1:59 PM ✅Answered | 1 vote

The meeting ID is stored on the DB of the user. If this is a permanent ID the user will always use this ID.

If the meeting ID will always create new, the meeting ID will always be assigned from the users pool 

regards Holger Technical Specialist UC


Wednesday, May 11, 2016 7:17 AM ✅Answered

Hi,

FrontEnd is hosting the meeting and meeting ID is written to the database. I'm pretty sure this is done from Frontend and not from the client. Client only send request to Frontend for new ID, which Frontend then writes to the database.

Clients doesn't write info to database directly, this is done thru frontend server

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work


Monday, May 16, 2016 11:57 AM ✅Answered

Hi,

Base on my understanding, the Lync meeting information is already be download to the local PC registry:

HKCU\Software\Microsoft\Office\15.0\Lync\ConfAddin\sip address

For your issue, you could delete the Lync meeting information from this path and then test again.

Best Regards

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Eason Huang
TechNet Community Support


Tuesday, May 10, 2016 5:11 PM

Agree with Holger.

You can also login to dialin.domain.com and reset your conf ID and meeting url (if your meeting is set to static)

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work


Wednesday, May 11, 2016 6:50 AM

That was my assumption as well. But as you see from my original post, the first message what I can find from the client trace is a SIP message which my client sent to Front End and that already includes the meeting ID. Based on my logic either A) client generate the ID by itself (do not believe) B) the meeting ID is received from Front End by some other process which is not write anything into trace log.

So the question is still: who is generating the ID and can we somehow trace it?

This gets even a bit more interested when you look the "Chapter_04_Conferencing_and_Collaboration.doc" from L2010 resource kit documentation. On the page 12 is says:

The flow for scheduling a conference can be broken up into three distinct steps.
1. The Online Meeting Add-in for Lync 2010 uses the Lync APIs and the Domain Name System (DNS) lookup or the manually configured server address to connect Outlook, through the Lync client, to the Focus Factory. The add-in then bundles the following information, required by the Focus Factory to create a conference, into a SIP SERVICE request:
*** - The conference ID***
* - A participant list*
* - User role information*
* - An expiration date*

I know it is L2010 documentation, but has this part really change so much..? But at least that time it really looks like client is the one generating the meeting ID.

Petri


Thursday, May 12, 2016 9:07 AM

I believe we all are "pretty sure" this is the way how it should go. But now when I look it a bit deeper, the facts seems to speak other language. The reason why I started to look this was pretty unique SIP errors:

SIP/2.0 503 syncReplicationFailed
SIP/2.0 400 conferenceAlreadyExists

The problem itself vanished without any good reasons, but still the logic of meeting ID is a bit unknown.

Petri