Multilevel precedence and preemption - Revision history

Nicole Tan at 19:44, 17 March 2015

2015-03-17T19:44:53Z

Nicole Tan at 18:58, 17 March 2015

2015-03-17T18:58:18Z

Nicole Tan at 18:57, 17 March 2015

2015-03-17T18:57:56Z

Nicole Tan at 18:57, 17 March 2015

2015-03-17T18:57:28Z

Nicole Tan: Modified the content to have clearer description

2015-03-17T18:56:23Z

Modified the content to have clearer description

Nicole Tan at 18:42, 17 March 2015

2015-03-17T18:42:16Z

Nicole Tan at 18:42, 17 March 2015

2015-03-17T18:42:03Z

Nicole Tan at 18:41, 17 March 2015

2015-03-17T18:41:51Z

Nicole Tan at 18:41, 17 March 2015

2015-03-17T18:41:40Z

Nicole Tan at 18:40, 17 March 2015

2015-03-17T18:40:17Z

@@ Line 21: / Line 21: @@
 | Relay MLPP information || MLPP fields are inserted in the outgoing leg only if they present in the incoming leg. The missing MLPP parameters from the incoming leg will be completed by the values of this profile.
 |-
-| Always insert MLPP information || MLPP fields are inserted in the outgoing leg. MLPP fields from the incoming leg will be used if available.
+| Always insert MLPP information || MLPP fields are inserted in the outgoing leg. MLPP fields from the incoming leg will be used if available. The missing MLPP parameters from the incoming leg will be completed by the values of this profile.
 |-
 | Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields will NOT be used.

@@ Line 25: / Line 25: @@
 | Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields will NOT be used.
 |}
 MLPP can be inserted or removed from the call flows. Depending on the networks involved, these are the results of the calls for different scenarios:

@@ Line 23: / Line 23: @@
 | Always insert MLPP information || MLPP fields are inserted in the outgoing leg. MLPP fields from the incoming leg will be used if available.
 |-
-| Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields will not be used.
+| Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields will NOT be used.
 |}

@@ Line 23: / Line 23: @@
 | Always insert MLPP information || MLPP fields are inserted in the outgoing leg. MLPP fields from the incoming leg will be used if available.
 |-
-| Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields from will not be used.
+| Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields will not be used.
 |}

@@ Line 19: / Line 19: @@
 | No MLPP insertion || No MLPP field is inserted in the outgoing leg.
 |-
-| Relay MLPP information || MLPP fields are inserted in the outgoing leg only if they were received in the incoming leg. The missing received parameters will be completed by the default values of this profile.
+| Relay MLPP information || MLPP fields are inserted in the outgoing leg only if they present in the incoming leg. The missing MLPP parameters from the incoming leg will be completed by the values of this profile.
 |-
 | Always insert MLPP information || MLPP fields are inserted in the outgoing leg. MLPP fields from the incoming leg will be used if available.
 |-
-| Forced MLPP information || MLPP profile fields are inserted in the outgoing leg. MLPP fields from the incoming leg will not be used.
+| Forced MLPP information || MLPP fields are always inserted in the outgoing leg by using the values of this profile. The incoming MLPP fields from will not be used.
 |}
-MLPP can be inserted or removed from the call flows. Depending on the networks involved, these are the results of the calls:
+MLPP can be inserted or removed from the call flows. Depending on the networks involved, these are the results of the calls for different scenarios:
 {| class="wikitable"
 |-
@@ Line 71: / Line 71: @@
 ! Incoming !! Outgoing
 |-
-| SS7 with or without MLPP || SS7: MLPP info from profile
+| SS7 with MLPP || SS7: incoming MLPP
 |-
-| SS7 with or without MLPP || SIP: Resource-Priority=q735.[precedence level from profile]
+| SS7 without MLPP || SS7: MLPP info from profile
 |-
-| SIP with or without resource priority || SS7: MLPP info from profile
+| SS7 with MLPP || SIP: Resource-Priority=q735.[incoming precedence level]
 |-
-| SIP with or without resource priority || SIP: Resource-Priority=q735.[precedence level from profile]
+| SIP Resource-Priority || SIP: Resource-Priority=q735.[precedence level from profile]
 |}

@@ Line 15: / Line 15: @@
 | '''4 possible MLPP outgoing modes'''
 |-
-! Option !! Explanation
+! Mode !! Explanation
 |-
 | No MLPP insertion || No MLPP field is inserted in the outgoing leg.