SIP Built-in Scripts

The “Call Hold” script is an extended version of the “Simple Call” script by adding a new demonstration of one caller places an existing call on-hold and then resumes the calls few minutes later.  The script performs the following functions:

• A and B register with a registrar.

• A connects to B

• A, B starts sending media to each other, wait for few minutes

• A places B on-hold, waits for few minutes and A resume calls with B.

• A, B starts sending media, wait for few minutes and stop media

• A disconnects from B.

.

The Call Forwarding – No Reply” script

CFNR script involves 3 participants (A, B, C) and an application-server (AS).  It demonstrates AS that forwards a call based on no-reply expiration time. The call is originated from A and is intended for B. B does not reply and AS cancels the dialog with and starts a new dialog with the new recipient C.

The “Simple Call” script is used for demonstrating a simple normal SIP call between 2 callers A and B.  The script performs the following functions:

• A and B register with a registrar.

• A connects to B

• A, B starts sending media to each other, wait for few minutes, and stop media

• A Disconnects from B.

The “Three Party Calls” script is used for demonstrating a conference call involving 3 callers and a conference server.  The message flow is configured to match the message flows of 3-Party Call in 3GPP TS 24.605 specification.  The script performs the following functions:

• A connects to B, starts media and place B on-hold

• A connects to C, start media and places C on-hold

• A connect to D (play as a conference server)

• A refers B to D

• B connects to D and disconnect from A

• A refers C to D

• C connects to D and disconnect from A

• A, B,C disconnects from D.

The Outgoing Call Barring script involves 2 participants (A, B) and an application-server (AS). It demonstrates AS that rejects an outgoing call from A if the media type in SDP offer matches configured media type.

1)     Call_CommunicationBarring (success, no auth) (A, B)

The “MSRP 5 Way Group Chat ” script is used for demonstrating a Group Chat Scenario involving 5 callers and a conference server. 

 The script performs the following functions:

The “Call Forwarding - Busy ” script is used for demonstrating a Call forwarding - busy. For example: Alice calls Bob, when Bob is busy, calls are forwarded to Carol. 

 The script performs the following functions:

The “Call Waiting” script is used for demonstrating a Call Waiting scenario. For example: Alice calls Bob, Bob places Alice on Call waiting, starts a conversation, and hangs up.

The script performs the following functions:

The “MSRP 5 way group chat HTTP file-transferring” script is used for demonstrating an HTTP File transferring scenario.

The script performs the following functions:

The “MSRP 5 way group chat MSRP file-transferring” script is used for demonstrating an MSRP File transferring scenario.

The script performs the following functions:

Part of the Mission Critical Push-To-Talk (MCPTT) services. Select to establish a MCPTT Private Call between A and B.

The script performs the following functions:

Part of the Mission Critical Push-To-Talk (MCPTT) services. Select to establish a MCPTT Prearranged Group Call among 5 subscribers.

The script performs the following functions:

Call Connect to VMS with RTP.

Retrieval without Callback.

Retrieval with Callback (INVITE)

Retrieval with Callback (REFER)

Retrieval with Callback (BYE Anonymous Call Rejection (ACR))

Call 610 script.

Part of the Mission Critical Push-To-Talk (MCPTT) services. Select to a MCPTT Private Call with Floor Control. Used by the MCPTT Floor Control feature. A Private Call is initiated towards an MCPTT Server (Subscriber C)

Part of the Mission Critical Push-To-Talk (MCPTT) services. Select to a MCPTT Group Call with Floor Control. Used by the MCPTT Floor Control feature. A Group Call is initiated towards an MCPTT Server.

The script accomplishes full scenario for Close Conference Group. Initiate Close Group Chat towards Conference Server. This is a licensed feature.

All Wait_For_Time steps set to value 1000 milliseconds.   Wait_For_Time in step 7 specifies data exchange time and it should be changed manually.

It consists of the next actions:

1.       Register

2.       Wait_For_Time

3.       Group_CallConnect (See SIP Built-in-Actions)

4.       Group_DataPathSetupMsrp

5.       Wait_For_Time

6.       Group_MediaStart

7.       Wait_For_Time

8.       Group_MediaStop

9.       Wait_For_Time

10.     Group_CallDisconnect

Roles:

In supplementary service’s flow four service roles are supported:

a.       Initiator (A)

b.      Participants (Invitees) (B)

c.       Confserver (C)

d.      NET

Initiator (A)

A is initiator, it sends a list of Invitees of (B) in XML body of INVITE message to confserver C. It includes all participants from B.  C performs Call Setup to each participant from B-list.

If B consists of 100 participant’s UEs, then we may specify the following operations:

• A (B1-B100) -> F – Initiator requests confserver to call all participants

Participants (B)

• In contrast to usage B as a UE in the case of big chatting group we consider it as participant list. If we do specify 100 UEs that B implies B1, B2…, and B100.

Confserver (C)

C is confserver.

• It receives INVITE request from Initiator (A) and calls all participants from the participant (invitees) list

• It receives request from A or any participant of B and forwards the received message to all participants from the group.