Sonus SBC 1000/2000 V8.0.0 IOT Skype for Business 2015 British Telecom Platform SIP Trunk Application Note

• DUT dials the number of BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of the BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of the BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of the BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT. Call should stay connected until released by DUT or BroadWorks user

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• BroadWorks User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• BroadWorks User dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of the BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT. Call should stay connected until released by DUT or BroadWorks user

BroadWorks to DUT; Wait for Session Timer (P1)

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• The call remains up to the session timer interval.
• A timer refresh request is sent.
• A successful response is sent to the timer refresh request.
• The call remains up and there is still a two-way voice path.
• Verify the session timer signaling per the instructions at the beginning of this test section.

BroadWorks to DUT; BroadWorks Holds, Wait for Session Timer (P1)

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• BroadWorks User A holds call using device hold mechanism.
• There is no voice path between BroadWorks User A and the DUT.
• The call remains up to the session timer interval.
• A timer refresh request is sent.
• The call remains up passed the session timer interval.
• BroadWorks User A retrieves held call by resuming the call at the device.
• The call remains up and a two-way voice path is re-established.
• Verify the session timer signaling per the instructions at the beginning of this test section.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• The call remains up to the session timer interval.
• A timer refresh request is sent.
• A successful response is sent to the timer refresh request.
• The call remains up and there is still a two-way voice path.
• Verify the session timer signaling per the instructions at the beginning of this test section.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• DUT holds call using device hold mechanism.
• There is no voice path between BroadWorks User A and the DUT.
• The call remains up to the session timer interval.
• A timer refresh request is sent.
• The call remains up passed the session timer interval.
• DUT retrieves held call by resuming the call at the device.
• The call remains up and a two-way voice path is re-established.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT audible locally supplied ringback.
• Verify the signaling to the DUT.
• BroadWorks sends 180 Ringing without SDP to the DUT.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• Make sure the DUT is rendering the remote ringback by removing the LAN connection from the remote endpoint.
  The ringback should stop. If it does not stop, then the DUT is ignoring the remote ringback and improperly generating local ringback.
• Verify the signaling to the DUT.
• BroadWorks sends SIP 18x with SDP.

• BroadWorks User A is alerted.
• DUT hears audible locally supplied ringback.
• After some number of rings, the call forwards and BroadWorks User B is alerted.
• DUT hears a remote ringback tone.
• Make sure the DUT is rendering the remote ringback by removing the LAN connection from the remote endpoint.
  The ringback should stop. If it does not stop, then the DUT is ignoring the remote ringback and improperly generating local ringback.
• Verify the signaling to the DUT.
• BroadWorks sends 180 Ringing without SDP to the DUT.
• BroadWorks sends SIP 18x with SDP. To-tag may change.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• Make sure the DUT is sending early media by removing the LAN connection from the DUT. The ringback should stop.
  If it does not stop, then the ringback is not being generated by the DUT.
• If double ringback occurs, check the signaling to see if the DUT sends an 18x with SDP followed by an 18x without SDP.
  If it does, see test setup step 2. If the RFC 3398 setting is required, make a note of this in the test report.
• Verify the signaling from the DUT.
• DUT sends SIP 18x with SDP.
• DUT may send additional SIP 18x with or without SDP.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• DUT is forwarded to voice mail and hears BroadWorks User A’s Voice Message No Answer greeting.
• Verify the signaling to the DUT.
• The TO tag in the 200 OK is different than the TO tag in 18x.
• The DUT ACKs the 200 OK.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible remote ringback.
• After some number of rings, BroadWorks User B is alerted.
• DUT receives audible remote ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established.
• Verify the signaling to the DUT.
• The TO tag in the second 18x is different from the TO tag in the first 18x.
• The TO tag in the 200 OK is different than the TO tag in the second 18x.
• The DUT ACKs the 200 OK.

• BroadWorks User A calls BroadWorks User B. User B answers.
• Two-way voice path is established.
• BroadWorks User B dials DUT via the CM.
• BroadWorks User A is put on hold.
• DUT is alerted.
• BroadWorks User B hears ringback.
• BroadWorks User B completes the transfer while DUT is ringing by clicking Transfer on the CM.
• BroadWorks User A hears ringback.
• DUT answers the call.
• Two-way voice path is established.
• Verify the signaling.
• DUT receives initial INVITE.
• DUT responds with 18x with SDP.
• DUT receives UPDATE with OFFER SDP.
• DUT responds to UPDATE with 200 OK with ANSWER SDP.

• BroadWorks User A calls DUT.
• DUT is alerted.
• BroadWorks User A receives remote ringback.
• The call CFNAs to another party or otherwise triggers UPDATE.
• BroadWorks User A still hears ringback.
• DUT answers the call.
• Two-way voice path is established.
• Verify the signaling.
• DUT responds with 18x with SDP.
• DUT sends UPDATE with OFFER SDP when the call forwards.
• The UPDATE is sent through to BroadWorks User A’s device.
• BroadWorks User A’s device responds to UPDATE with 200 OK with ANSWER SDP.

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT hears audible remote ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• Verify the signaling to the DUT.
• BroadWorks sends an 18x with early-offer to the DUT.
• The DUT sends a PRACK with early-answer.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A hears audible remote ringback.
• DUT answers the call.
• Two-way voice path is established.
• Verify the signaling to the DUT.
• DUT sends an 18x with early-offer.
• BroadWorks sends a PRACK with early-answer.

• DUT dials BroadWorks User A.
• BroadWorks User B is alerted.
• DUT receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call clears.
• Verify the signaling to the DUT.
• BroadWorks sends a 181 Call is Being Forwarded response to the DUT.
• BroadWorks sends a 180 or 183 to the DUT.
• The TO tag in the 180/183 or 200 OK may be different than the TO tag in 181.

• DUT dials an international number (prefixed by “00” ).
• Verify the signaling from the DUT.
• DUT sends SIP INVITE with Request-URI containing the international number dialed, 00xxxxxxxxx@<sip-domain>.

• DUT dials the extension for BroadWorks User A (xxxx#).
• Verify the signaling from the DUT.
• DUT sends SIP INVITE with Request-URI containing the extension dialed, 1234@<sip-domain> or 1234#@<sip-domain>.

• DUT dials the feature access code (*xx).
• Verify the signaling from the DUT.
• DUT sends SIP INVITE with Request-URI containing the feature access code, *73@<sip-domain>.

• DUT dials the feature access code (*xx*).
• Verify the signaling from the DUT.
• DUT sends SIP INVITE with Request-URI containing the feature access code, *21*@<sip-domain>.

• DUT dials the Auto Attendant.
• DUT hears a greeting and a prompt provided by the Auto Attendant.
• DUT responds to the Auto Attendant prompts and supplies the necessary digits to transfer the call to BroadWorks User A.
• BroadWorks User A is alerted.
• DUT hears audible ringback.
• Verify the signaling from the DUT.
• DUT sends INVITE to BroadWorks without the RFC 2833 payload type in the SDP.

Verify the following:

• DUT dials the Auto Attendant.
• DUT hears a greeting and a prompt provided by the Auto Attendant.
• DUT responds to the Auto Attendant prompts and supplies the necessary digits to transfer the call to BroadWorks User A.
• BroadWorks User A is alerted.
• DUT hears audible ringback.
• Verify the signaling to/from the DUT.
• DUT sends INVITE to BroadWorks with the RFC 2833 payload type in the SDP.

Example: rtpmap:101 telephone-event/8000

• Verify the BroadWorks returns an SDP without the RFC 2833 payload type.
• Inspect the RTP to ensure that there is no RFC 2833 DTMF sent by the DUT.

• DUT dials the Auto Attendant.
• DUT hears a greeting and a prompt provided by the Auto Attendant.
• DUT responds to the Auto Attendant prompts and supplies the necessary digits to transfer the call to BroadWorks User A.
• BroadWorks User A is alerted.
• DUT hears audible ringback.
• Verify the signaling to/from the DUT.
• DUT sends INVITE to BroadWorks with the RFC 2833 payload type in the SDP.

Example: rtpmap:101 telephone-event/8000

• Verify the BroadWorks returns an SDP with the RFC 2833 payload type.
• Inspect the RTP to ensure that RFC 2833 DTMF is sent by the DUT.

• DUT dials the Auto Attendant.
• DUT hears a greeting and a prompt provided by the Auto Attendant.
• DUT responds to the Auto Attendant prompts and supplies the necessary digits to transfer the call to BroadWorks User A.
• BroadWorks User A is alerted.
• DUT hears audible ringback.
• Verify the signaling to/from the DUT.
• DUT sends SIP INFO messages for DTMF-relay.
• DUT does not send inband or RFC 2833 DTMF in addition to DTMF-relay.

• BroadWorks User A dials BroadWorks User B.
• BroadWorks User B is alerted.
• BroadWorks User A receives audible ringback.
• DUT dials *98 to pick up the call.
• Two-way voice path is established between the DUT and BroadWorks User A.
• Verify the signaling.
• Inspect the SDP in the 200 OK from DUT in response to reINVITE without SDP from BroadWorks.
• The SDP must contain all of the DUT’s supported and enabled codecs.
• The version in the o-line must be incremented.

NOTE: SfB rejects the call with 491 (SF00500447)

• BroadWorks User A dials BroadWorks User B.
• BroadWorks User B is alerted.
• BroadWorks User A receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established.
• BroadWorks User A dials a second call to Call Park feature code *68 to park the call.
• BroadWorks User A hears IVR announcement requesting a number to park the call against.
• BroadWorks User A supplies the DUT extension to park the call against.
• BroadWorks User A hears IVR announcement indicating the call has been parked.
• BroadWorks User B is now held.
• BroadWorks User A hangs up.
• DUT dials *88+<DUT DN> to retrieve the parked call.
• Two-way voice path is established between the DUT and BroadWorks User B.
• Verify the signaling to/from the DUT.
• BroadWorks sends HOLD SDP in the 200 OK answer to the initial INVITE from the DUT.
• BroadWorks sends a re-INVITE with B’s SDP to the DUT.
• DUT sends 200 OK to BroadWorks with ANSWER SDP.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established between BroadWorks User A and the DUT.
• BroadWorks User A uses the CM to blind transfer the DUT to BroadWorks User B by entering BroadWorks User B’s extension and selecting the Transfer button.
• BroadWorks User A is released.
• BroadWorks User B is alerted.
• DUT receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established between BroadWorks User B and the DUT.
• Verify the SIP signaling and RTP.
• Check initial 200 OK and RTP stream to determine negotiated codec between BroadWorks User A and the DUT.
• During the transfer, BroadWorks sends the DUT a re-INVITE without SDP.
• DUT responds with 200 OK containing OFFER SDP.
• BroadWorks sends ACK containing ANSWER SDP.
• Check 200 OK and RTP stream to determine negotiated codec between BroadWorks User B and the DUT.
  This must be different from the codec negotiated with BroadWorks User A

• BroadWorks User A dials the BroadWorks User B.
• BroadWorks User B is alerted.
• BroadWorks User A receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established between BroadWorks User A and BroadWorks User B.
• BroadWorks User A uses the CM to call the DUT by entering the DUT’s extension and selecting the Dial button.
• BroadWorks User B is held.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established between BroadWorks User A and the DUT.
• BroadWorks User A uses the CM to transfer BroadWorks User B to the DUT by selecting Transfer.
• BroadWorks User A is released.
• Two-way voice path is established between BroadWorks User B and the DUT.
• Verify the SIP signaling and RTP.
• Check initial 200 OK and RTP stream to determine negotiated codec between BroadWorks User A and the DUT.
• During the transfer, BroadWorks sends the DUT a re-INVITE without SDP.
• DUT responds with 200 OK containing OFFER SDP.
• BroadWorks sends ACK containing ANSWER SDP.
• Check 200 OK and RTP stream to determine negotiated codec between BroadWorks User B and the DUT.
  This must be different from the codec negotiated with BroadWorks User A.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established between BroadWorks User A and the DUT.
• DUT holds the call by using the DUT’s hold mechanism.
• The call is held (no voice path in either direction).
• BroadWorks User A uses the CM to blind transfer the DUT to BroadWorks User B by entering BroadWorks User B’s extension and selecting the Transfer button.
• BroadWorks User A is released.
• BroadWorks User B is alerted.
• DUT does not receive audible ringback, as the call is still on hold.
• BroadWorks User B answers the call.
• Call is still held (no voice path in either direction).
• DUT retrieves the held call.
• Two-way voice path is established between BroadWorks User B and the DUT.
• Verify the SIP signaling and RTP.
• Check initial 200 OK and RTP stream to determine negotiated codec between BroadWorks User A and the DUT.
• DUT sends re-INVITE with hold SDP.
• DUT sends re-INVITE to resume.
• Check 200 OK and RTP stream to determine negotiated codec between BroadWorks User B and the DUT.
  This must be different from the codec negotiated with BroadWorks User A.

• DUT is restarted.
• Verify the SIP signaling to/from the DUT.
• DUT sends GIN REGISTER request to BroadWorks for the PBX main line or pilot number.

Example:

REGISTER sip:enterprise.com SIP/2.0
Via: SIP/2.0/UDP 10.16.145.102:5060;branch=z9hG4bK-c64fe4c
From: <sip:+13441004000@enterprise.com>;tag=54321
To: <sip:+13441004000@enterprise.com>
Contact: <sip:192.0.2.100;bnc>;expires=3600
Call-ID: 98765abcde
CSeq: 28337 REGISTER
Max-Forwards: 70
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Require: gin
Proxy-Require: gin
Supported: path
Content-Length: 0

• BroadWorks responds with 200 OK.

• BroadWorks User A dials the DUT (to a PBX user, not the PBX main line).
• DUT is alerted.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• DUT hangs up the call.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• BroadWorks sends an INVITE to the DUT with the PBX user number in the Request-URI and To headers.
• After answer, DUT sends 200 OK.

• DUT (PBX user, not the PBX main line) dials BroadWorks User A.
• BroadWorks User A is alerted.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• DUT hangs up the call.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• DUT sends an INVITE with the PBX user number in the From.
• After answer, BroadWorks sends 200 OK.

• BroadWorks User A dials the DUT.
• The call forwards immediately to BroadWorks User B.
• BroadWorks User B is alerted.
• BroadWorks User A receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established.
• BroadWorks User B hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The DUT sends a 302 redirect with the PBX user’s number in a Diversion or History-Info header.
• Alternatively, the DUT sends a new INVITE with BroadWorks User A’s number in the From and the DUT’s number in a Diversion or History-Info header.

• DUT PBX user dials the DUT PBX user with Call Forwarding enabled.
• The call forwards immediately to BroadWorks User B.
• BroadWorks User B is alerted.
• DUT PBX user receives audible ringback.
• BroadWorks User B answers the call.
• Two-way voice path is established.
• BroadWorks User B hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The first INVITE from DUT PBX user to DUT PBX user must be internal to the PBX, not sent to BroadWorks.
• For the Call Forward, the DUT sends a new INVITE with the calling DUT’s number in the From and the forwarding DUT’s number in a Diversion or History-Info header.

• First DUT PBX user dials second DUT PBX user.
• Second DUT PBX user is alerted.
• First DUT PBX user receives audible ringback.
• Second DUT PBX user answers the call.
• Two-way voice path is established.
• Second DUT PBX blind transfers the call to BroadWorks User B.
• BroadWorks User B is alerted.
• First DUT PBX user receives audible ringback.
• BroadWorks User B hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The first INVITE from DUT PBX user to DUT PBX user must be internal to the PBX, not sent to BroadWorks.
• For the Call Transfer, the DUT sends a new INVITE with the calling DUT’s number in the From and the forwarding DUT’s number in a Diversion or History-Info header.

• BroadWorks User A dials the DUT.
• DUT is alerted.
• DUT endpoint displays the calling name and number for BroadWorks User A.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The INVITE from BroadWorks to the DUT does not contain Privacy headers (P-Asserted-Identity and Privacy) and From header contains the originator's calling name and number.

Example:
From:"Bill Jameson"<sip:+12408888130@as.broadworks.net;user=phone>;tag=1525954323-1216666352531

• BroadWorks User C dials the DUT.
• DUT is alerted.
• DUT endpoint displays “Anonymous” or other indication of a restricted call.
  The DUT endpoint must not display the calling name or number.
• BroadWorks User C receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• BroadWorks User C hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The INVITE from BroadWorks to the DUT does not contain Privacy headers (P-Asserted-Identity and Privacy).
  The From header should also be encrypted as anonymous.

Example:
From:<sip:anonymous@anonymous.invalid>;user=phone>;tag=1525954323-1216666352531

• BroadWorks User A dials the DUT.
• DUT is alerted.
• DUT endpoint displays the calling name and number for BroadWorks User A.
  The Unicode characters in the Calling Name are properly displayed.
• BroadWorks User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• BroadWorks User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The INVITE from BroadWorks to the DUT does not contain a Privacy headers (P-Asserted-Identity and Privacy). From header contains the originator’s calling name and number. The caller name contains Unicode characters.

Example:
From:"Björk Guðmundsdóttir "<sip:+12408888130@as.broadworks.net;user=phone>;tag=1525954323-1216666352531

• DUT dials BroadWorks User A.
• BroadWorks User A is alerted.
• BroadWorks User A endpoint displays calling name and number.
• Note that BroadWorks sends the DUT’s calling name and number as configured on BroadWorks to the remote endpoint.
  This overrides the name and number as sent in the INVITE from the DUT, so it may differ.
• DUT receives audible ringback.
• BroadWorks User A answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The INVITE from the DUT to BroadWorks contains a Privacy header set to “none” and P-Asserted-Identity and From headers containing the originator’s calling name and number.

Example:
From:"Scott Bean"<sip:+13018881001@as.broadworks.net;user=phone>;tag=1525954323-1216666352531

P-Asserted-Identity:"Scott Bean"<sip:+13018881001@as.broadworks.net;user=phone
Privacy:none

• DUT dials BroadWorks User C.
• BroadWorks User C is alerted.
• BroadWorks User C’s endpoint displays “Anonymous” or other indication of a restricted call.
• DUT receives audible ringback.
• BroadWorks User C answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• The INVITE from the DUT to BroadWorks contains a Privacy header set to “id”. The P-Asserted-Identity header contains the originator’s calling name and number. The From header may also be encrypted as anonymous.

Example:
From:<sip:anonymous@anonymous.invalid>;user=phone>;tag=1525954323-1216666352531

P-Asserted-Identity:"Scott Bean"<sip:+13018881001@as.broadworks.net;user=phone
Privacy: id

• DUT dials 999.
• Early operator is is alerted.DUT receives audible ringback.
• Early Operator answers the call and verifies the CLI
• Two way voice path is established.
• Emergency operator floats the call to the emergency agent.
• Three way call is established.
• Early operator leaves the call.
• Two way call between DUT and emergency agent continues.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials 999.
• Early operator is is alerted.DUT receives audible ringback.
• Early Operator answers the call and verifies the CLI.
• Two way voice path is established.
• Emergency operator floats the call to the emergency agent.
• Three way call is established.
• Early operator leaves the call.
• Two way call between DUT and emergency agent continues.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials 112.
• Early operator is is alerted.DUT receives audible ringback.
• Early Operator answers the call and verifies the CLI.
• Two way voice path is established.
• Emergency operator floats the call to the emergency agent.
• Three way call is established.
• Early operator leaves the call.
• Two way call between DUT and emergency agent continues.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials 112.
• Early operator is is alerted.DUT receives audible ringback.
• Early Operator answers the call and verifies the CLI.
• Two way voice path is established.
• Emergency operator floats the call to the emergency agent.
• Three way call is established.
• Early operator leaves the call.
• Two way call between DUT and emergency agent continues.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of PSTN User A.
• PSTN User A is alerted.
• DUT receives audible ringback.
• PSTN User A answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT
• Make sure the DUT sends all messages to the primary Application Server address.

• PSTN User A dials the DUT.
• DUT is alerted.
• PSTN User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• PSTN User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• DUT dials the number of PSTN User A.
• PSTN User A is alerted.
• DUT receives audible ringback.
• PSTN User A answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT
• Make sure the DUT sends all messages to the primary Application Server address.

• PSTN User A dials the DUT.
• DUT is alerted.
• PSTN User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• PSTN User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• PSTN User A dials the DUT, with 141 preceding the DUTs number.
• DUT is alerted.
• PSTN User A receives audible ringback.
• DUT answers the call.
• Two-way voice path is established.
• PSTN User A hangs up.
• The call is released upon disconnect.
• Verify the SIP signaling to/from the DUT.
• Make sure the DUT sends all messages to the primary Application Server address.

• Apply 'Calling Line ID Blocking' on business portal for the DUT. DUT dials the number of PSTN User A.
• PSTN User A is alerted.
• DUT receives audible ringback.
• PSTN User A answers the call.
• Two-way voice path is established.
• DUT hangs up.
• The call is released.
• Verify the SIP signaling to/from the DUT
• Make sure the DUT sends all messages to the primary Application Server address.