SIP NAMES REQUIRED FOR AMTMITEL

[John Richard Procter]

For monitoring of the sip trunks DATATEX will need the NETWORK ELEMENT name.

SIPPEER20160523.PNG

The existing MiTAI SXMonitor function will now support monitoring SIP trunks (referred to as Peer monitoring). A new attribute, SX_PEER_NAME, is used to monitor a SIP trunk. The SX_PEER_NAME attribute value is a MiVoice Business Network Element name associated with a SIP trunk. All SIP trunk calls for the Network Element will be reported as MiTAI call status events to the Peer monitor.

To specify a Network Element name programmed for a SIP trunk. The size of a name is restricted to 9 characters maximum and no hyphen( ‘-‘).

Behavioural changes in Public Trunk :

The participants involved in a SIP Trunk call can change. For example, the call is transferred/ forwarded over SIP trunk to a different participant.
In scenarios with changing participants, all participants should have access to updated information showing the current call participants.
To get this information in MiTAI events, the options below are set in MiVoice Business for SIP Peer.

Go to SIP Peer Profile-> Signalling and Header Manipulation
Allow Display Update ----------- Yes
Use P-Asserted Identity Header ---------- Yes

Recommendation for SIP Trunk as a public Trunk: The SIP Trunk as a public trunk is supposed to carry corporate name and number only. When a SIP trunk is used as a public trunk, CPN (Calling Party Number) must be configured in MiVoice Business. Not configuring CPN may cause incorrect participants information in MiTAI events. CPN substitution is typically used to show the customer's corporate name and number for all outgoing calls to the public network.