In this example, an enterprise owner connects the PTT Pro group Hardware to applications that generate text messages and announcements.
Interworking PTT Pro Audio
The customer administrator adds an IWG endpoint to ZEMS with the following information:
The Site (PTT Pro department) includes the Hardware group. The department must exist in the
PTT Pro
and be synced to ZEMS before it can be used to create an IWG endpoint.
Target type is Group. A PTT Pro user or a PTT Group are possible target types for the endpoint. The name of the group in this example is Hardware.
The endpoint name, Hardware, in this example.
The proxy name of Hardware_Proxy.
When the administrator adds the endpoint, ZEMS performs the following actions:
ZEMS adds a user to the
PTT Pro Server
with the specified proxy name, in this example, Hardware_proxy. If the user already exists in the
PTT Pro Server
, the IWG uses the existing user.
ZEMS adds the user Hardware_Proxy to the Hardware group if it is not already a member of the group.
ZEMS adds the PTT_Pro_Hardware endpoint to the IWG with the proxy of Hardware_proxy. As a result of adding Hardware_proxy as the proxy, ZEMS registers with the
PTT Pro Server
as the user Hardware_proxy.
When the IWG receives an announcement or message intended for the PTT_Pro_Hardware endpoint, the IWG forwards the communication from the Announcer or Messenger to the Hardware group using the proxy user Hardware_Proxy.
When an announcement or message is forwarded from the Announcer or Messenger to the Hardware group, the originator is identified by the proxy name, Hardware_proxy, in this example.
The following diagram shows how Sites in ZEMS correspond to departments in the PTT Pro server. When you add an IWG endpoint, the proxy user is added as a PTT Pro user. If the target of the IWG endpoint is a group, as in this example, the proxy user is added as a group member.
