The test passes if the following two conditions are met:
Routing Decisions displays data similar to the following: < sip:12345@MyOtherCompany.com > to SIP Entity ’CalledPartySIPentity’ port ’MyPortNumber’ using TCP/TLS/UDP
Routing Decisions Process displays data similar to the following:
NRP Sip entities: Originating SIP Entity is SIP Entity Name
Using digits < 12345 > and host < MyOtherCompany.com > for routing.
NRP Dial Patterns: No matches for digits < 12345 > and domain < MyOtherCompany.com >
NRP Dial Patterns: No matches for digits < 12345 > and domain < null >
NRP Dial Patterns: No matches found for the originator’s location. Trying again using NRP Dial Patterns that specify -ALL- locations.
NRP Dial Patterns: No matches for digits < 12345 > and domain < MyOtherCompany.com >
NRP Dial Patterns: Found a Dial Pattern match for digits < 12345 > and domain < null >.
Ranked destination NRP Sip Entities: ’CalledPartySIPentity’
Removing disabled routes.
Ranked destination NRP Sip Entities: ’CalledPartySIPentity’
Adapting and proxying to SIP Entity ’CalledPartySIPentity’
NRP Adaptations: Doing ingress adaptation.
NRP Adaptations: Changed P-Asserted-Identity header to sip: 67890@MyCompany.com as part of adaptation.
NRP Adaptations: Doing egress adaptation.
Routing < sip: 12345@MyCompany.com > to SIP entity ’CalledPartySIPentity’ port ’MyportNumber’ using TCP/TLS/UDP.
Note:
Calls with multiple possible destinations will display multiple rows.
