Overview:
Feature 1580 adds to the IMG the ability to accept an incoming SIP NOTIFY request (outside of a subscription) which has the parameters Event type = message summary and Content Type = application/simple-message-summary and interwork these messages into an SS7 network using TCAP messaging. SIP uses the SIP Specific Event Notification (Notify) as a mechanism to transport the MWI message through IP and the IMG then inter-works the Notify message along with its Event Package Name "simple-message-summary" to the SS7/Outgoing side. The IMG then receives a response from the SS7 network and inter-works this response to the SIP network and sends the response out in the 200 OK message. This feature supports RFC 3842 section 5.2 only. This feature was initially added in software version 10.5.2 but was supported using the ANSI protocol only. In software version 10.5.3 the MWI functionality for ITU was added. For more information on this feature, see Related Topics below.
Diagram:
Call Flow Diagram:
SIP to SS7:
Call Trace Example (Incoming SIP):
14:17:47.393 CALL(SIP) (00:00001:00)
---> [10.129.55.37, 5060]
NOTIFY sip:8473339552@10.129.55.50 SIP/2.0\r\n
Event:message-summary\r\n
Via: SIP/2.0/UDP 10.129.55.37:5060\r\n
Max-Forwards: 70\r\n
From: sip:8003330002@10.129.55.37:5060\r\n
To: sip:8473339552@10.129.55.50\r\n
Call-ID: 1-2464@10.129.55.37\r\n
Cseq: 1 NOTIFY\r\n
Contact: <sip:8003330002@10.129.55.37:5060>\r\n
Content-Type: application/simple-message-summary\r\n
Content-Length: 42\r\n
\r\n
Messages-waiting: yes\r\n
Voice-Message: 1/0
14:17:47.393 CALL(SIP) (00:00001:00) RCVD NOTIFY from 10.129.55.37:5060 udp
14:17:47.393 CALL(SIP) (00:00001:00) with Via sent-by: 10.129.55.37
14:17:47.393 CALL(SIP) (00:00001:00) NOTIFY request without matching subscription
14:17:47.393 CALL(SIP) (00:00001:00) SENT Route Control to L4
14:17:47.393 CALL(L4) (00:00001:00) RCVD Route Control from SIP
14:17:47.393 CALL(L4) (00:00001:00) Accessing Route Table 2
14:17:47.393 CALL(L4) (00:00001:00) Accessing Resource Table 1
14:17:47.393 CALL(L4) (00:00001:00) SENT Route Control Ack to SIP
14:17:47.393 CALL(SIP) (00:00001:00) RCVD Route Control Ack from L4
14:17:47.393 CALL(SIP) (00:00001:00) Session Group Profile ID is 1
14:17:47.393 CALL(SIP) (00:00001:00) Messages-Waiting: yes
14:17:47.393 CALL(SIP) (00:00001:00) SENT Service Request to GCL
14:17:47.393 CALL(GCL) (00:00001:00) RCVD Service Request from SIP
14:17:47.393 CALL(GCL) (00:00001:00) Incoming Channel Group = 12 [Workstation]
14:17:47.393 CALL(GCL) (00:00001:00) Invoke TCAP MWI Service
14:17:47.393 CALL(GCL) (00:00001:00) Stack 0x00 SSN 0xf7 Dialog 0x00000001
14:17:47.393 CALL(GCL) (00:00001:00) SENT PPL Event TC Query w/Permission Primi tive Set to TUSI
14:17:48.473 CALL(GCL) (00:00001:00) RCVD PPL Event for TCAP dialog 0x00000001
14:17:48.473 CALL(GCL) (00:00001:00) PPL Event TC Response Primitive Set
14:17:48.473 CALL(GCL) (00:00001:00) Dialog primitive TC Response
14:17:48.473 CALL(GCL) (00:00001:00) Component primitive TC Result L
14:17:48.473 CALL(GCL) (00:00001:00) MWI TCAP SUCCEEDED
14:17:48.473 CALL(GCL) (00:00001:00) SENT Service Response to SIP
14:17:48.473 CALL(SIP) (00:00001:00) RCVD Service Response from GCL
14:17:48.473 CALL(SIP) (00:00001:00) SENT 200 OK NOTIFY to 10.129.55.37:5060 UDP
14:17:48.473 CALL(SIP) (00:00001:00)
<--- [10.129.55.37, 5060 <- 10.129.55.50, 5060]
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 10.129.55.37:5060;received=10.129.55.37
\r\n
Call-ID: 1-2464@10.129.55.37\r\n
From: sip:8003330002@10.129.55.37:5060\r\n
To: sip:8473339552@10.129.55.50;tag=a94c095b773be1dd6e8d
668a785a9c8461fdca52\r\n
Contact: <sip:8473339552@10.129.55.50:5060>\r\n
CSeq: 1 NOTIFY\r\n
Server: Dialogic-SIP/10.5.2.67 1010_NODE_0 0\r\n
Event: message-summary\r\n
Content-Length: 0\r\n
\r\n
TCAP Query w/Response (ANSI)
Hex Representation
LSByte......MSByte 83 00 07 07 07 46 aa 01 09 80 03 0b 10 08 89
LSByte......MSByte 00 f7 48 37 33 59 25 05 c3 f7 07 46 aa 2d e2
LSByte......MSByte 2b c7 04 10 2b 00 01 e8 23 e9 21 cf 01 01 d0
LSByte......MSByte 02 8a 01 f2 18 aa 16 84 09 06 00 11 0a 48 37
LSByte......MSByte 33 59 25 84 09 0c 00 11 0a 08 30 33 00 20
Checksum CRC 16............ 1001101100111011 hex=9b3b
Decoded Message
octet 003 Service information octet | |
10...... | Network indicator. N National network |
....0011 | Service indicator. SCCP Signalling Connection Control Part |
..00.... | Message priority.. 0 |
octet 004 Routing Label | |
........ | DPC: Net-Clstr-Mbr 007-007-000 STP0 |
........ | OPC: Net-Clstr-Mbr 170-070-007 SG |
00000001 | SLS............... 1 |
octet 011 SCCP Message type | |
00001001 | Headers H1/H0..... UDT Unitdata |
....0000 | Protocol class.... 0 |
1000.... | Message handling.. Return message on error |
00000011 | Pointer-> Called # 3 |
00001011 | Pointer-> Call'g # 11 |
00010000 | Pointer-> Data.... 16 |
octet 016 Called Party Address | |
00001000 | Parameter length.. 8 |
.......1 | SSN indicator..... Address contains a Subsystem Number |
......0. | SPC indicator..... No Signalling Point Code in Address |
..0010.. | Global Title...... GT includes Translation type |
.0...... | Routing basis..... RoutingBasedOnGlobalTitleInTheAddress |
1....... | Address indicator. Nat'l address, coded to nat'l specification |
00000000 | Subsystem name.... ? SSN not known/not used |
11110111 | Translation type.. Translation type |
........ | Address digits.... 8473339552 |
octet 025 Calling Party Address | |
00000101 | Parameter length.. 5 |
.......1 | SSN indicator..... Address contains a Subsystem Number |
......1. | SPC indicator..... Address contains Signalling Point Code |
..0000.. | Global Title...... No Global Title included |
.1...... | Routing basis..... RoutingBasedOnLabelDPC&SSNinCalledNumbr |
1....... | Address indicator. Nat'l address, coded to nat'l specification |
11110111 | Subsystem name.... ? Spare/Network Specific |
........ | SPC: Net-Clstr-Mbr 170-070-007 SG |
octet 031 SCCP user data | |
00101101 | SCCP data length.. 45 |
octet 032 Calling Party Address | |
11100010 | Package type...... QURYP Query,W/ permission,Nat'l,constructr |
00101011 | Total TCAP length. 43 |
11000111 | Transaction ID.... Transaction ID Identifier, Nat'l, primitive |
00000100 | Xaction ID length. 4 |
........ | Originating ID.... 16788240 |
octet 040 Dialogue/Component Portion | |
11101000 | Portion Identifier Component Sequence |
00100011 | Component length.. 35 |
11101001 | Component Type Id. INVKL InvokeLast, National, constructor |
octet 043 TCAP Message, Component portion | |
00100001 | Component length.. 33 |
11001111 | Component ID ident Component ID identifier, National, primitive |
00000001 | Compon't ID length 1 |
00000001 | Invoke ID......... 1 |
11010000 | Op Code identifier National TCAP, National, primitive |
00000010 | Op Code length.... 2 |
.0001010 | Operation family.. Report Event |
1....... | Reply required?... Yes, reply required |
00000001 | Op specifier...... Voice Message Available |
octet 051 Parameter Tag | |
11110010 | Parameter Tag..... [18] Private/Constructed |
00011000 | Parameter Len .... 24 |
octet 053 Parameter Tag | |
10101010 | Parameter Tag..... Service Key |
00010110 | Parameter length.. 22 |
octet 055 TCAP Parameter | |
10000100 | Parameter Ident... Digits |
00001001 | Parameter length.. 9 |
00000110 | Digit type........ Destination Number |
00000000 | Nature of number.. No Presentation Restriction, National |
....0001 | Encoding.......... BCD odd number of digits |
0001.... | Numbering plan.... ISDN Numbering Plan (Rec E.164) |
00001010 | Number of digits.. 10 |
........ | Address digits.... 8473339552 |
octet 066 TCAP Parameter | |
10000100 | Parameter Ident... Digits |
00001001 | Parameter length.. 9 |
00001100 | Digit type........ VMSR Identifier |
00000000 | Nature of number.. No Presentation Restriction, National |
....0001 | Encoding.......... BCD odd number of digits |
0001.... | Numbering plan.... ISDN Numbering Plan (Rec E.164) |
00001010 | Number of digits.. 10 |
........ | Address digits.... 8003330002 |
Checksum | CRC 16............ 1001101100111011 hex=9b3b |
Additional Information:
This feature does not support outgoing SUBSCRIBE message and will not generate an outgoing NOTIFY message with content type application/simple message-summary.
Maximum Number of TCAP dialogs is limited to 32768.
IMG will accept incoming NOTIFY request outside of a subscription as long as Event is message-summary and Content-Type is application/simple-message-summary.
IMG will return a 484 "Subscription does not exist" for any NOTIFY requests with Event and Content Types being something other displayed above.
Request for TCAP Service sent from NOTIFY shall contain user information from R-URI and FROM: URI in UPDF format.
Notify shall send a 200 OK or 4xx/5xx response based on response sent from SS7 side.
Feature 1580 MWI will not support outgoing SUBSCRIBE.
IMG Software version 10.5.2 supports ANSI only for this feature. In software version 10.5.3, support for the ITU protocol was added.
Gate Control Layer will create a unique dialog ID for the TCAP request. The ID will be 4 bytes long. First two bytes are used for a counter and last two are used to store NODE ID:
A timer is enabled after Gate Control Layer sends PPL Event Request to SS7. If no Event Indication is received after a timer expires the Gate Control Layer will send a clear to SIP. (4xx/5xx)
IMG will not generate an outgoing INVITE with TCAP request.
F-1580 Message Waiting Indicator is supported with SS7 redundancy.
If configuring a service such as CNAM or MWI on multiple IMG nodes, the SS7 Stack ID's cannot be configured with the same ID. For example, when configuring an IMG Node 0 with stack ID's 0 and 1 then any other IMG Nodes configured under any Logical Node can not have any of the stacks configured with the same ID's (0 or 1). By doing so, the TCAP services cannot be configured.
Related Topics:
IMG 1010 - Configuring Message Waiting Indicator - SIP to SS7