8.2 SipStack

The following table lists the SipStack ErrorIds, numbered 1000 – 1999, generated by the OCS front-end server and Access Edge Server for releases prior to the most current release.

ErrorId

Header

SIP Request,

Response

Reason

1000

ms-diagnostics

Response

Final handshake failed.

1001

ms-diagnostics

Response

From URI not authorized to communicate with public IM providers.

1002

ms-diagnostics

Response

From URI not authorized to communicate with federated partners.

1003

ms-diagnostics

Response

User does not exist.

1004

ms-diagnostics

Response

Route set is no longer valid.

1005

ms-diagnostics

Response

Cannot route to destination domain.

1006

ms-diagnostics

Response

Error routing on protocol client connection.

1007

ms-diagnostics

Response

Temporarily cannot route.

1008

ms-diagnostics

Response

Unable to resolve DNS SRV record.

1009

ms-diagnostics

Response

Conflicting SRV and host domains in DNS.

1010

ms-diagnostics

Response

Certificate trust with next-hop server could not be established.

1011

ms-diagnostics

Response

ms-diagnostics header not provided by previous hop.

1012

ms-diagnostics

Response

From URI is not authorized to communicate with users outside the enterprise.

1013

ms-diagnostics

Response

Significant time skew detected during authentication.

1014

ms-diagnostics

Response

Unable to resolve DNS A record.

1015

ms-diagnostics

Response

Cannot route from message source domain.

1016

ms-diagnostics

Response

Message asserted domain traffic type does not match source domain.

1017

ms-diagnostics

Response

Cannot route from external domain to external domain on external edge.

1018

ms-diagnostics

Response

Parsing failure.

1019

ms-diagnostics

Response

Referred-By header parameters are not valid.

1020

ms-diagnostics

Response

Identity of the referrer could not be verified with the ms-identity parameter.

1021

ms-diagnostics

Response

Integrity of the referrer information could not be verified with the ms-identity-cookie parameter.

1022

ms-diagnostics

Response

Cannot process routing destination.

1023

ms-diagnostics

Response

The destination domain of the message resolved to a peer of an incompatible type.

1024

ms-diagnostics

Response

Message boss (on-behalf-of) domain traffic type does not match source domain.<7>

1025

ms-diagnostics

Response

Allowed partner domain resolved by DNS SRV to a fully qualified domain name (FQDN) that matches a different routing rule.<8>

1026

ms-diagnostics

Response

Domain resolved by DNS SRV to multiple FQDNs that match different routing rules.<9>

1027

Ms-diagnostics

Response

Cannot route this type of SIP request to or from federated partners.<10>