Can someone give me a simpler explanation of what Origination DNs are for - OCS?

[nonny]

From the Outbound Deployment Guide:

<quote>
If any other DNs of the ACD Queue, Routing Point, External Routing Point,
Service Number, Virtual Queue types or any others are involved in an
outbound call flow, they must be monitored by OCS. These DNs should be
specified as an Origination DN in the Advanced tab of the Agent Group or
Place Group object that is linked to the Campaign Group in order for OCS to
register those DNs with T-Server and to receive call-related events on those
DNs.
</quote>

If the DN in question (the route point for the strategy that is played on answer) is on a particular switch, wouldn't it be sufficient that OCS has a connection to the TServer for that switch?

<quote>
Note: If a Voice Transfer Destination DN and a T-Server used as a Dialer,
belong to one switch in a multi-site environment, but the call is
distributed by external routing to an agent who is on a different site, at
least one queue from this site should be listed in the Origination DN
list of the corresponding Agent or Place Group. This forces OCS to
register regular DNs on the remote site and receive related events.
</quote>

In my environment, the route point is on SIP Server/Switch and the call is eventually routed to agents on a Cisco TServer/switch.  So it may be obvious but does this refer to creating a VQ for something (the agent campaign group??) on the Cisco side or on the SIP side and put that VQ into the origination list on the Campaign Agent Group?  I've seen environments with no Origination DNs configured at all so not sure I understand this correctly.

[Fra]

[quote author=nonny link=topic=8935.msg39933#msg39933 date=1434965215]
From the Outbound Deployment Guide:

<quote>
If any other DNs of the ACD Queue, Routing Point, External Routing Point,
Service Number, Virtual Queue types or any others are involved in an
outbound call flow, they must be monitored by OCS. These DNs should be
specified as an Origination DN in the Advanced tab of the Agent Group or
Place Group object that is linked to the Campaign Group in order for OCS to
register those DNs with T-Server and to receive call-related events on those
DNs.
</quote>

If the DN in question (the route point for the strategy that is played on answer) is on a particular switch, wouldn't it be sufficient that OCS has a connection to the TServer for that switch?
[/quote]

No. The reason why Origination DNs must be specified is for OCS to be able to create a 'map' of the DNs involved in the flow that targets each outbound agent group.
If OCS had only the connection with TServer specified, regardless of what DNs OCS would register, it would get one single massive list of DNs that would be utterly useless to determine the aforementioned.
That is necessary to track the incoming traffic and determine for instance the agent availability in predictive campaigns.

[quote author=nonny link=topic=8935.msg39933#msg39933 date=1434965215]
<quote>
Note: If a Voice Transfer Destination DN and a T-Server used as a Dialer,
belong to one switch in a multi-site environment, but the call is
distributed by external routing to an agent who is on a different site, at
least one queue from this site should be listed in the Origination DN
list of the corresponding Agent or Place Group. This forces OCS to
register regular DNs on the remote site and receive related events.
</quote>

In my environment, the route point is on SIP Server/Switch and the call is eventually routed to agents on a Cisco TServer/switch.  So it may be obvious but does this refer to creating a VQ for something (the agent campaign group??) on the Cisco side or on the SIP side and put that VQ into the origination list on the Campaign Agent Group?  I've seen environments with no Origination DNs configured at all so not sure I understand this correctly.
[/quote]
This is referring to the need of specifying additional DN(s) to allow what I described above. OCS must be aware of where calls where distributed from: whether that's a RP or VQ on the premise switch, that depends on a number of factors.

Fra

[nonny]

Thanks.  So giving the high level setup as follows

CommunicationDN and OCS Trunk Group on SIP Switch.  Trunk also on SIP switch for routing to the PSTN via a CUBE.  Route Point that has strategy loaded is also on SIP switch.  Answered calls are routed to agents via that strategy with the agents situated on the Cisco switch.

I would then add the SIP RP in the Origination List, and create a VQ on the Cisco switch for that agent group and also use it in the Target block within the strategy and add that VQ to the Origination List as well?  Should I also then be adding the Trunks as they are involved in the call flow?

[Fra]

[quote author=nonny link=topic=8935.msg39935#msg39935 date=1434973057]
I would then add the SIP RP in the Origination List, and create a VQ on the Cisco switch for that agent group and also use it in the Target block within the strategy and add that VQ to the Origination List as well?
[/quote]
Yes.

[quote author=nonny link=topic=8935.msg39935#msg39935 date=1434973057]
Should I also then be adding the Trunks as they are involved in the call flow?
[/quote]
No. Trunk DNs don't generate the typical TLib event flow that OCS monitors, plus calls are delivered 'through' a Trunk straight to agents - we're talking here about queues / RPs.