SIP agent deskphones must have dedicated SIP trunk groups for:
Procedure
Add SIP trunks on the Private Numbering and the Public Unknown Numbering screens.
Do not add extra digits to station extensions and agent extensions on the Private Numbering or the Public Unknown Numbering screens. The extra digits might cause Session Manager to send calls to Communication Manager for further processing without terminating the calls to the 96X1 SIP agent deskphones. If private unknown numbering modifies agent extensions, an agent can log out and log in to a station but cannot use a feature button to change the work state.
Ensure that Session Manager has two entities for Communication Manager: One for inbound traffic and the other for agent deskphone traffic. All SIP trunks must be on the Processor Ethernet (PE) interface.
Ensure that the signaling groups for the deskphone SIP OPS signaling trunk groups have a listen port number that is different from the listen port number of the inbound SIP trunking signal groups and that the trunk groups are dedicated for each function.
The Session Manager Profile configuration for the SIP agent deskphones must point to the Communication Manager entity that has been defined for the OPS trunk (station) signaling in the Origination Application Sequence field and the Termination Application Sequence field. Otherwise, the appropriate station signaling trunks are not used to deliver calls to the SIP agent deskphones. This is important with an existing configuration that uses the same Communication Manager entity for all traffic and now you want to separate it into dedicated inbound trunking and OPS signaling trunking.
Administer Sequenced Applications for users based on whether the user is on the originating or on the terminating side of a call. When designing sequences for applications that act on the deskphones that are controlled by Communication Manager Evolution Server, Communication Manager must be the last application defined on the origination side of a call and the first application defined on the termination side of the call. An Evolution Server must be the last application in the origination sequence and the first application in the termination sequence because the Evolution Server uses the full call model for call processing and all origination and termination feature processing occurs on the origination side of the call. For more information, see Implementing End-to-End SIP.
For dedicated trunk groups that are used for agent deskphone signaling with Session Manager, you must administer the Measured field on the Trunk Group screen as none to prevent Call Management System (CMS) or Avaya IQ reporting issues, including loss of reporting.
