Manual Chapter :
Did the message reach the message
router?
Applies To:
Show Versions
BIG-IP LTM
- 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
Did the message reach the message
router?
There are multiple places where processing can stop or a failure can occur. The stats of the
profiles added to the virtual server (or transport-config) should be used to determine if the
message reached the message router. From the transport profile's stats (TCP/UDP/SCTP), it can be
determined if packets were received by the transport filter. From the protocol profile's stats
(sipsession), it can be determined if the received packets were correctly parsed into messages.
If an error was found in the message parsing this should be detectable using the protocol's
stats.
The message router profile (siprouter) stats should increment with each message received. The
result of each messages routing operation should also be represented in the stats.
Why did the message fail routing
The MR_INGRESS event is raised for each message before it enters routing . Once routing is
complete either MR_EGRESS or MR_FAILED event is raised. The message metadata can be logged during
these events to help debug the results of routing. Some fields and their usage follows:
Metadata Field | Populated | Purpose |
|---|---|---|
lasthop | before MR_INGRESS | Contains the TMM and flow_id of the originating connection of the message |
nexthop | before MR_INGRESS (or during MR_INGRESS) | Selects the destination connection for the message |
route | after routing (or during MR_INGRESS) | The value of the selected route (peer list). If set during MR_INGRESS, this route will
be used instead of performing route lookup |
originator | before MR_INGRESS | The IP, port and rtdom_id of the originator of the connection. Also contains the
transport type and name of the originating connection. |
status | after routing | The results of the route lookup |
attempted | after routing (or during MR_INGRESS) | The list of destination hosts attempted. This list of hosts will be treated as marked
down when performing peer selection and load balanced pick. |
retry_count | after routing | The number of times this message has been submitted for routing |
