Adapter sends the XML message
A2W_NotifyUserEnter using HTTP post to WebEx Meetings using the WbxHostName associated with the conference. Parameter ExtCallID is null.
WebEx Meetings returns a confirmation message Confirmation in the return HTTP post notifying the adapter the request was received.
WebEx Meetings changes the Web user / meeting status to reflect that a user entered the event. WebEx Meetings checks the ExtCallID
parameter in the A2W_NotifyUserEnter. If the parameter is null, and this is a
call-in user, WebEx Meetings generates a new external call ID for it.
WebEx Meetings sends W2A_RspNotifyUserEnter message to the adapter using the adapter host name given in the WebEx Meetings configuration
file, and returns the new External ID and the original MsgID given in A2W_NotifyUserEnter.
The adapter sends a confirmation message in the return HTTP post confirming the message was received and then associates the
External ID with the Bridge ID.
User Call Out
WebEx Meetings sends the XML message W2A_Callout to adapter using HTTP post to pass a valid external call ID.
The adapter returns a confirmation message in the return HTTP post.
The adapter works with the bridge trying to issue a call out.
The adapter is notified by the bridge that the call out was successful, and sends an A2W_RspCallout message to
WebEx Meetings.
WebEx Meetings returns a confirmation message.
The adapter receives a notice from the bridge when the call-out user enters the conference. It then sends an
A2W_NotifyUserEnter message with a valid External Call ID obtained from WebEx Meetings.
WebEx Meetings returns a confirmation message.
When WebEx Meetings finds parameter ExtCallID is valid, it knows this is a call-out user and there is no need to
generate a new External ID for the user.
WebEx Meetings sends a W2A_RspNotifyUserEnter message to the adapter with the valid External Call
ID parameter.
The adapter returns a confirmation message, and re-associates the External Call ID with the Bridge Call ID (re-associating is good practice).
