Sacred локальная сеть ошибка 10026

Overview

В данном руководстве вы узнаете как поиграть онлайн в Sacred через удобный и практичный лан-эмулятор RadminVPN.

Введение

Официальные сервера Sacred закрылись в 2009-2010 году, с тех пор игра с другими игроками через интернет возможна лишь через эмуляторы локальной сети (LAN-эмуляторы).

В 2018 году закрылся Tunngle — основной LAN-эмулятор для Sacred, а вскоре после него закрылся и альтернативный Evolve.

В Steam есть функция “Remote Play Together” для совместной игры через эмуляцию сети, но она поддерживает ограниченное количество человек и не поддерживает моды с измененным EXE-файлом, да и далеко не все играют в Sacred от Steam.

Поэтому у игроков возникает вопрос: “А как поиграть по сети?”
В данном руководстве вы узнаете как поиграть в Sacred по сети через RadminVPN.

Скачиваем RadminVPN[www.radmin-vpn.com] и устанавливаем его.

Я выбрал RadminVPN, так как он не требует регистрации, обладает отличным функционалом, максимально прост и интуитивно понятен.

ПРИМЕЧАНИЕ: После установки RadminVPN добавится в автозапуск и будет автоматически запускаться при включении компьютера. Если вам это не нужно, то уберите RadminVPN из автозапуска (как это сделать легко найти в любом поисковике). Иногда, после обновлений RadminVPN вновь может добавиться в автозапуск.

После запуска RadminVPN вы увидите вот такое окно:

Красная кнопка рядом с именем служит для подключения/отключения, нажмите на нее, чтобы подключиться.

В выпадающем меню «Система» вы можете изменить своё имя в RadminVPN и выбрать язык программы.

В выпадающем меню «Сеть» вы можете создать сеть или подключиться к уже существующим сетям. В RadminVPN с обновлением 1,1 появились специальные игровые сети для различных игр, они нам и нужны.

Подключение к игровой сети

Нажимайте «Сеть» → «Присоединиться к существующей сети».

В открывшемся окне выбирайте вкладку «Игровая сеть».

Вводите в поле «Поиск» название нужной игры, в нашем случае Sacred.

Для игры Sacred есть две сети — Sacred и Sacred Underworld, можете использовать любую. Нажимаете на сеть и жмёте «Присоединиться» в правом нижнем углу окна.
ПРИМЕЧАНИЕ: Сеть Sacred Underworld чисто логически по названию предпочтительней, так как последняя версия Sacred — это Sacred с дополнением Underworld, он же Sacred Gold.

Создание сервера в Sacred

После того, как вы подключились к сети в RadminVPN, вам нужен игровой север на котором вы сможете играть. Вы можете подключиться к серверам других игроков (если они есть), либо создать свой. В этом разделе мы рассмотрим именно создание сервера, а непосредственно подключение – в следующем разделе.

Создать сервер может ЛЮБОЙ ЖЕЛАЮЩИЙ, в этом нет ничего сложного, не пугайтесь слова «сервер». Создать сервер можно через саму игру, но я настоятельно рекомендую создавать сервер через “Gameserver.exe“, расположенный в папке с игрой.

В отличие от созданного через саму игру сервера, Gameserver.exe более гибко настраивается, активен не зависимо от присутствия на нём создающего игрока, и его можно запустить многократно.

После запуска Gameserver.exe вы увидите следующее окно:

• IP address — выставляйте тот IP, который у вас в RadminVPN. IP идут списком, но отображается лишь пара строчек, поэтому вам может потребоваться пролистать их колёсиком мыши.
• Game name — имя сервера, вводите что хотите.
• TCP Port (1024-32767) — указывайте любое значение из диапазона. Если будете создавать несколько серверов сразу, то это значение у них должно быть разным.
• Password — пароль, который нужно будет ввести, чтобы войти на сервер. Оставьте пустым, чтобы сервер был без пароля, либо введите любой пароль на ваш вкус, если хотите, чтобы никто не мог зайти на сервер не зная пароля.
• Internet/LAN — ставьте точку на LAN, так как мы играем через LAN-эмулятор локальной сети.

Далее нажимаем «OK». Вы увидите следующее окно:

Столбик слева с позициями 01-16 — это находящиеся на сервере игроки.

Из верхних выпадающих меню нас интересуют лишь «Game Configuration» и «Session Tools».

«Game Configuration» позволит установить режим сервера, сложность и количество игроков:

• Free Game — режим сервера «Свободная игра». В этом режиме нельзя сохранять сюжетный прогресс, а вся территория открыта. Максимальное количество человек для этого режима — 16.
• Playerkiller Game — то же, что Free Game, но с возможностью атаковать других игроков, не состоящих с вами в группе. Максимальное количество человек для этого режима — 16.
• Campaign Game — режим сервера «кампания Анкария». В этом режиме открыта территория Анкарии и доступна основная сюжетная линия, а первый игрок на сервере может сохранять сюжетный прогресс (в том числе прогресс побочных заданий и убитых боссов). Максимальное количество человек для этого режима — 4.
• Campaign Underworld — режим сервера «кампания Underworld». В этом режиме открыта вся территория и доступна сюжетная линия дополнения, а первый игрок на сервере может сохранять сюжетный прогресс (в том числе прогресс побочных заданий и убитых боссов). Максимальное количество человек для этого режима — 4.
• Bronze Difficulty — сложность сервера «Бронза». На эту сложность могут заходить игроки 1-60 уровня.
• Silver Difficulty — сложность сервера «Серебро». На эту сложность могут заходить игроки 20-100 уровня.
• Gold Difficulty — сложность сервера «Золото». На эту сложность могут заходить игроки 60-140 уровня.
• Platinum Difficulty — сложность сервера «Платина». На эту сложность могут заходить игроки 100-180 уровня.
• Niobium Difficulty — сложность сервера «Ниобий». На эту сложность могут заходить игроки 140-216 уровня.
• Change num of players — изменение количества игроков.

«Session Tools» позволит приостановить действия на сервере, закрыть вход на сервер, отправить сообщение всем или конкретному игроку от лица сервера, выгнать игрока, установить игровое время, а также выставить погодные эффекты на сервере.

• Lock Session — закрыть вход на сервер. Игроки не смогут зайти на сервер, пока вы не откроете его, но уже зашедшие останутся на сервере.
• Pause Session — приостановка сервера (режим паузы).
• Send message to all stations — отправить сообщение для всех от лица сервера.
• Send private message — отправить сообщение какому-либо игроку от лица сервера. Нужно будет указать номер игрока из списка слева.
• Kick player — выгнать игрока с сервера. Нужно будет указать номер игрока из списка слева.
• Set ingame time — установить игровое время на сервере.
• Set Rain — включить дождь.
• Set Fog — включить туман.
• Set Snow — включить снег.
• Set Lightning — включить грозу.
• Set Earthquake — включить землетрясение.

ПРИМЕЧАНИЕ: Погодные эффекты могут не полностью отображаться на низких настройках графики.

Вход на сервер

Для входа на сервер в главном меню нажимаем «Сетевая игра».

Затем «Локальная сеть» (мы ведь играем через эмулятор локальной сети).

Затем выбираем экспортированного героя или создаём нового на пьедестале экспорта, и жмём «Далее».

Находим нужный сервер в списке серверов, выбираем его и нажимаем «Вступить».

Вводим пароль, если он есть, и нажимаем «Начать игру».
Если ранее вы сохраняли прогресс кампании, то в соответствующем режиме можете продолжить его, нажав на «Загрузить» и выбрав сохранение.

После этого вы окажитесь на сервере и можете играть.

Возможные проблемы и их решение

Не видно сервера

Либо сервер запущен неверно (не тот IP или при создании сервера выбран «Internet», а не «LAN»), либо что-то блокирует RadminVPN, сам Sacred.exe или Gameserver.exe. Блокировать может антивирусник, брандмауэр/Firewall, DEP.
Рекомендуется добавить RadminVPN, Sacred.exe и Gameserver.exe в исключения этих защит, либо вообще эти защиты отключить.
Иногда бывает, что добавление в исключения почему-то не помогает и нужно именно выключать! (Есть реальный пример, знаю человека, которому приходится именно выключать брандмауэр).

Также мешать может другой LAN-эмулятор. Нужно отключить сетевой адаптер другого LAN-эмулятора, либо вообще удалить этот LAN-эмулятор (хотя отключения адаптера должно хватать).

Не стоит забывать и о банальном режиме совместимости для «Gameserver.exe», возможно, это тоже сможет помочь.

Еще на форумах был найден следующий совет:
У кого не видно комнаты попробуйте выставить метрику 1.
1.Заходим в центр управления сетями
2.Находим Radmin VPN адаптер.
3.Нажимаем “Свойства”, далее выбираем протокол IP версии 4 и жмем “Свойства”.
4.Далее жмем дополнительно, снимаем галку с автоматической метрики и вписываем цифру 1.

Ошибка «CODE – 20 Kernel: Cannot allocate logdata message»

Это довольно распространённая, однако быстро решаемая проблема. Всё что вам нужно сделать – это сменить тип подключения в настройках игры. Если у вас галочка стоит на первом пункте, переставьте её на второй и наоборот, если галочка стоит на втором пункте. Перезапустите игру и подключитесь к серверу.

Ошибка «CODE – 10026 Socket: Connected time out without connection»

Как правило, такая ошибка вылезает если у сервера выставлен неверный IP.

Несовместимые данные

Сервер запущен с какой-то модификацией баланса, а вы пытаетесь зайти без неё. Либо наоборот – у вас какая-то модификация баланса, а на сервере её нет.

Неверная версия

Либо ваша версия игры не совпадает с версией игры создавшего сервер (последняя официальная версия 2.28), либо сервер запущен с ReBorn Mod.

Заключение

На этом всё.
В руководстве описаны все известные проблемы и их решения, однако, это не всем помогает. Если вы знаете ещё какие-то решения проблем или знаете чем можно дополнить данную статью — напишите об этом автору или в комментариях.

Дополнительно: Частные сети в RadminVPN

В этом разделе рассмотрены создание частной сети, подключение к частным сетям и существующие частные сети для Sacred, которые больше ненужны после появления игровых сетей. Если хотите, можете смело пропустить этот раздел, информация в нём необзяательная.

Создание частной сети

При желании вы можете создать свою частную сеть, нажав «Сеть» → «Создать новую сеть».

Никаких сложностей с этим возникнуть не должно, так как нужно лишь ввести название сети и пароль. Можете поставить галочку в «Разрешить отправку запросов на подключение без пароля», чтобы люди могли подключаться к вашей сети без пароля.

Подключение к частной сети

Для подключения к частной сети нажмите Нажимайте «Сеть» → «Присоединиться к существующей сети».

В появившемся окне выберите «Частная сеть». Вам нужно будет указать имя сети и пароль (если требование к нему не отключено создателем сети), чтобы к ней присоединиться.

Частные сети для Sacred

Ранее, до введения в RadminVPN игровых сетей, были только частные сети и мы предлагали всем игрокам подключаться к нашей частной сети, чтобы все собрались в одном месте. Сейчас в этом больше нет нужды, однако, сети остались и ниже вы можете найти две наиболее популярные сети:

Сеть русского сообщества VK-SacredWiki[vk.com] от OverLookers[vk.com]:

• Название сети: SacredWiki (S и W заглавные, остальные строчные).
• Пароль: olksbest (все буквы строчные).

Сеть зарубежного сообщества Darkmatters.org (они же SacredWiki.org):

• Название сети: darkmatters.org
• Пароль: sacredwiki

Некоторые пользователи Windows сталкиваются с кодом ошибки 10053 при попытке подключить свой компьютер с помощью почты SMTP или при попытке выполнить команду Winsock. Эта проблема обычно связана с ограничениями маршрутизатора, чрезмерно защищающими брандмауэрами или прокси-серверами и VPN.

После изучения этой конкретной проблемы выяснилось, что существует несколько различных причин, которые могут вызывать этот код ошибки. Вот краткий список потенциальных виновников:

Метод 1. Отключение или удаление избыточных антивирусных программ (если применимо)

Если вы используете сторонний пакет, вы сталкиваетесь с кодом ошибки 10053 при попытке выполнить определенное действие, связанное с вашим почтовым клиентом (например, загрузка или отправка электронной почты через VPOP3), скорее всего, эта проблема вызвана вашим программа-антивирус.

По словам некоторых затронутых пользователей, эта проблема часто вызвана определенными версиями McAfee VirusScan и Norton Antivirus – это всего лишь две сторонние антивирусные программы, которые мы обнаружили, но может быть и другое программное обеспечение, вызывающее такую ​​же проблему.

Если этот сценарий выглядит так, как будто он может быть применим, вы должны начать с отключения защиты в реальном времени и посмотреть, перестает ли возникать код ошибки – в большинстве пакетов AV вы можете отключить защиту в режиме реального времени, щелкнув правой кнопкой мыши панель в трее. значок и ищет параметр, который отключит экраны в реальном времени.

Щелкните правой кнопкой мыши значок Avast на панели задач, чтобы временно отключить Avast

Если отключение защиты в реальном времени не привело к устранению проблемы, следуйте приведенным ниже инструкциям, чтобы удалить проблемный пакет со своего компьютера и удалить все остаточные файлы, чтобы устранить проблему:

Если та же проблема все еще возникает после удаления вашего стороннего пакета или этот метод не применим, перейдите к следующему потенциальному исправлению ниже.

Метод 2: Выполнение полного сброса TCP / IP

Если код ошибки 10053 возникает сразу после разрыва соединения TCP / IP в Windows, скорее всего, это проблема с тайм-аутом передачи данных или ошибкой протокола. Как выясняется, это, скорее всего, вызвано сбоями в работе сетевого адаптера или классическим случаем неправильного диапазона DNS.

По словам некоторых затронутых пользователей, эту проблему иногда можно решить, выполнив полный сброс TCP / IP на каждом компьютере, входящем в состав локальной мастерской.

Если вы не знаете, как это сделать, следуйте приведенным ниже инструкциям, чтобы выполнить полный сброс TCP / IP из командной строки с повышенными привилегиями:

Метод 3: перезагрузка или сброс маршрутизатора / модема

Если приведенные выше команды Winsock не устранили проблему в вашем случае, вам следует продолжить, исключив текущую сеть из списка потенциальных виновников.

По мнению некоторых затронутых пользователей, эта проблема также может возникать в тех случаях, когда ваш интернет-провайдер назначает динамический IP-адрес, который конфликтует с определенными параметрами SMTP.

В случае, если этот сценарий применим, есть два способа решить проблему и избежать получения кода ошибки 10053:

Если вы планируете или применяете этот метод, мы советуем начать с простого перезапуска и переходить ко второй процедуре только в том случае, если первое вспомогательное руководство (A) не решает проблему:

A. Перезагрузка роутера / модема

Если вы хотите решить проблему без сброса каких-либо конфиденциальных данных, которые в настоящее время хранятся на вашем маршрутизаторе или модеме, это способ сделать это.

Чтобы выполнить перезагрузку (перезагрузку) маршрутизатора, обратите внимание на заднюю часть сетевого устройства и нажмите кнопку включения / выключения, чтобы выключить устройство. После этого также отсоедините кабель питания от розетки, к которой он в данный момент подключен, и подождите целую минуту, чтобы убедиться, что силовые конденсаторы полностью разряжены.

Перезагрузка роутера

После того, как вам удастся перезапустить маршрутизатор, обязательно отключите кабель питания и подождите целую минуту, чтобы убедиться, что силовые конденсаторы полностью разряжены, прежде чем возобновлять питание.

По истечении этого периода повторно подключите кабель питания и дождитесь восстановления доступа к Интернету, прежде чем повторять действие, которое ранее вызывало код ошибки.

Если та же проблема все еще возникает, перейдите к следующему потенциальному исправлению ниже.

Б. Сброс маршрутизатора / модема

Если в вашем случае первый метод не сработал, скорее всего, вы имеете дело с более серьезным несоответствием, которое коренится в меню настроек вашего маршрутизатора или модема.

В этом случае вам следует сбросить маршрутизатор или модем до заводского состояния, восстановить доступ в Интернет и посмотреть, закончится ли эта операция исправлением ошибки 10053.

Важно: прежде чем принудительно выполнить эту операцию, имейте в виду, что в конечном итоге будут удалены все настройки, которые вы ранее установили для своего маршрутизатора. Это будет включать любые сохраненные учетные данные PPPoE, внесенные в белый список или заблокированные сообщения и перенаправленные данные TCP / IP.

Чтобы инициировать сброс маршрутизатора или модема, найдите кнопку сброса (обычно она находится на задней панели маршрутизатора). Когда вам удастся найти его, нажмите кнопку сброса и удерживайте ее нажатой в течение 10 секунд или пока не заметите, что все светодиоды устройства мигают одновременно.

Сброс маршрутизатора

Примечание. Для большинства моделей маршрутизаторов вам понадобится острый предмет, чтобы можно было нажать и удерживать кнопку сброса.

После завершения процедуры сброса дождитесь восстановления доступа к Интернету, затем посмотрите, исправлен ли теперь код ошибки 10053. Имейте в виду, что если ваш интернет-провайдер использует PPPoE, вам нужно будет повторно вставить правильные учетные данные, прежде чем доступ в Интернет будет восстановлен.

Если этот сценарий неприменим или вы уже пробовали это безуспешно, перейдите к следующему потенциальному исправлению ниже.

Метод 4: отключите прокси или VPN-соединение (если применимо)

Если ни один из вышеперечисленных методов не устранил проблему в вашем случае, и вы используете VPN-клиент или прокси-сервер, чтобы скрыть происхождение вашего подключения, это, скорее всего, является источником ошибки 10053.

Нам удалось найти множество пользовательских отчетов, в которых утверждалось, что эта конкретная ошибка была вызвана либо клиентом VPN, либо прокси-сервером, который был принудительно применен на системном уровне.

В зависимости от используемого вами решения по обеспечению анонимности вы сможете решить проблему, отключив прокси-сервер или полностью удалив VPN на системном уровне.

Мы рассмотрели оба возможных сценария, поэтому не стесняйтесь следовать одному из нижеприведенных руководств, чтобы отключить прокси-сервер системного уровня или удалить VPN-клиент:

A. Удаление VPN на уровне системы

Б. Отключение прокси-сервера

10061 подключение не установлено

Как устраняется проблема

Запустить (стартовать) службу Агента сервера 1С:Предприятие.

После установки какого-либо софта, при входе в агент сервера 1С или запуске игры у любого пользователя может выскочить ошибка “Подключение не установлено, т. к. конечный компьютер отверг запрос на подключение”. Эта проблема проявляется и при работе в какой-нибудь программе – она при этом попросту закроется, и вылезет окошко с вышеуказанным сообщением. Сегодня мы разберем существующие методы решения этой ошибки.

Что вызывает ошибку «подключение не установлено, т. к. конечный компьютер отверг запрос на подключение»

Скачок напряжения и потеря связи с серверами

К счастью, справиться с этим довольно просто.

Все, можно заново устанавливать соединение с сервером. Этот способ можно применить и в тех случаях, когда возникает ошибка с кодом 0000000002, т. к. в результате какого-либо сбоя любая служба может быть остановлена.

Проблема возникает в торренте

Брандмауэр или антивирус не разрешают соединение

Если антивирус или брандмауэр “ругаются” и не дают подключиться к серверу, то для исправления ошибки есть два варианта.

Отключить и один, и другой	Это допустимо только в том случае, если мы уверены, что во время бездействия “защитников” не поймаем какой-нибудь вредоносный код
Добавьте проблемный порт в список исключений брандмауэра	Он пропустит сетевой трафик по указанному порту, и работа будет налажена.

Одно из популярных мест, где возникает данная ошибка – софт 1С. Проблема в том, что агент сервера 1С и все процессы запущены, но тут появляется ошибка и сообщение о том, что “Подключение не установлено, т. к. конечный компьютер отверг запрос на подключение”. Решаем мы данную проблему тем, что добавляем порт 10061 в исключения брандмауэра и снова устанавливаем соединение с сервером.

Добавляем отмеченный порт 10061 в исключения брандмауэра

Важно: всегда используем только самую свежую версию 1С. Читаем о том, где получить обновления, в статье об ошибке под номером 0400300003.

Решение проблем с частной локальной сетью

Вызываем реестр через строку “Выполнить”

Редактируем записи реестра

Там же мы обязательно выставляем настройки брандмауэра (FirewallRules).

Другие причины появления ошибки

Многие пользователи пытаются при возникновении проблемы сразу снести установленную операционную систему, но этого делать не нужно.

По крайней мере, пока мы не убедились, что проблема не с нашим устройством, а на сторонних ресурсах:

Мы постарались разобраться в способах исправления ошибки “Подключение не установлено, т. к. конечный компьютер отверг запрос на подключение”. Если у вас есть другие реальные способы решения этой проблемы, описывайте их в комментариях.

Бывает, однажды, ни с того и с чего программа 1С нам выдает: Ошибка соединения с сервером 1С:Предприятие Не запущен ни один рабочий процесс. Соединение с базой невозможно.

Несколько вариантов поиска ошибок и решений:

1. Глюк сервака — всякое бывает

Остановите в диспетчере задач процессы: ragent rphost rmngr и Запустите службу «Агент сервера 1С:Предприятие»

2. При внезапном отключения питания или аналогичных ситуациях — повредился файл srvribrg. lst

Нужно удалить все из папки srvinfo

Запустите службу «Агент сервера 1С:Предприятие».

Через Администрирование серверов 1С Предприятия по новой создать кластер 1С и добавить информационные базы

3. Переименовали сервер на котором служба агента 1С

После переименования сервера Windows Server 2008 с установленным 1С:Предприятие 8.2, перестала работать служба «Агент сервера 1С:Предприятие 8.2». Она запускается, работает несколько секунд и останавливается. Если подключаться к серверу 1С:Предприятие 8.2 через консоль серверов, то возникает ошибка:

Ошибка соединения с сервером 1С:Предприятие 8.2 server_addr=tcp://SERVER:1540 descr=Ошибка сетевого доступа к серверу (Windows Sockets — 10061(0x0000274D). Подключение не установлено, т. к. конечный компьютер отверг запрос на соединение.) line=590 file=.SrcDataExchangeTcpClientItmpl. cpp

При подключении к базе на этом сервере имеем следующую ошибку:

Не запущен ни один рабочий процесс. Соединение с базой невозможно.

При подключении оборудования произошла ошибка 999 в Атол

В конце рабочего дня кассиры вынуждены закрывать отчёты на своих рабочих местах. Но по непонятным причинам возникает сбой, и появляется сообщение «При подключении оборудования произошла ошибка» (999) в Атол. Что это значит и как решить эту проблему — читайте в этой статье далее.

Ошибка 999 в Атол – каковы причины?

Тестирование 1С платформы при подключении оборудования

Для этого перейдите в настройки РМК:

Такая рекомендация может помочь в случае сбоев программы. Модуль пытается отыскать неверный код и исправить его. Попробуйте выйти из тестирования и попытаться подключиться к кассе.

Проверка драйвера

Выполните следующие действия:

Когда драйвер будет установлен, следует снова вернуться в это окно, чтобы убедиться, что всё в порядке. Это нужно сделать обязательно, так как если вы сами установили драйвер, который нашли в сети, он может не подойти к версии ОС или её разрядности.

Рассмотрим способ настройки драйвера Атол, когда появляется сбой 999. Для этого нужно нажать на кнопку « Пуск » в Windows.

После этого открываем 1С предприятие и открываем смену. Если такой способ не помог решить ошибку при подключении оборудования 999 в Атол, попробуйте следующую инструкцию.

Изменение протокола и канала устройства Атол

В зависимости от модели устройства Атол, его настройки могут отличаться.

Таким образом, вы сможете выбрать для кассового аппарата Атол необходимый канал и протокол обмена. Попробуйте изменить их, если появляется ошибка подключения оборудования 999 в кассовом устройстве Атол. В противном случае, при неудачно подключении, попытайтесь обратиться в техническую поддержку или к системному администратору.

Diagnostic ID
Reason
Description

0
Server Internal Error
Server internal error

1
Service Unavailable
Service unavailable

2
See response code and reason phrase
Default error code used by a component if it is adding only one ms-diagnostics header for all failure scenarios

3
Invalid forwarding location
The server cannot forward request originally addressed to the TO user to the location specified in the request URI

4
Insufficient bandwidth to establish session. Do not attempt re-route
There is not sufficient bandwidth to establish the session. Do not attempt to reroute this session request

5
Insufficient bandwidth to establish session. Attempt PSTN re-route
There is not sufficient bandwidth to establish the session. Attempt to reroute request to establish session

6
Insufficient bandwidth to establish session. PSTN reroute blocked for caller
There is not sufficient bandwidth to establish the session. Caller’s user Policy block the call from being re-routed through PSTN

15
Dialog route set update failed
Recovery action to update dialog route set failed

16
Registration route set update failed
Recovery action to re-register and update dialog route set failed

17
Wait for dialog route set update timed out
Timed out waiting for the remote party to update the dialog route set

21
Call failed to establish due to a media connectivity failure where one endpoint is of unknown type
The call failed to establish due to a media connectivity failure.  The unknown endpoint is most likely a legacy client, legacy component or third party application. The most common cause for this is that a legacy client in the conversation needs to be patched (KB 2028888). This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server.  Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

22
Call failed to establish due to a media connectivity failure when both endpoints are internal
The call failed to connect because a media path could not be established between the two internal endpoints. This can be caused by network performance issues affecting the endpoints. Correlation of such failures with individual networks or endpoints can indicate potential deployment issues.

23
Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote
The call failed to connect because a media path could not be established between an internal endpoint and a remote endpoint. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

24
Call failed to establish due to a media connectivity failure when both endpoints are remote
The call failed to connect because a media path could not be established between two remote endpoints. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

25
A federated call failed to establish due to a media connectivity failure where both endpoints are internal
A federated call failed to connect because a media path could not be established between the two internal endpoints. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

26
A federated call failed to establish due to a media connectivity failure where one endpoint is internal and the other is remote
A federated call failed to connect because a media path could not be established between the two parties. This is a federated call where one endpoint is internal and the other is remote. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

27
A federated call failed to establish due to a media connectivity failure where both endpoints are remote
A federated call failed to connect because a media path could not be established between the two remote endpoints. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

28
A public service provider call failed to establish due to a media connectivity failure with an internal endpoint
A call with a public service provider failed to connect because a media path could not be established between the the external provider and an internal endpoint. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

29
A public service provider call failed to establish due to a media connectivity failure with a remote endpoint
A call with a public service provider failed to connect because a media path could not be established between the the external provider and a remote endpoint. This failure can be caused by network performance issues affecting the endpoints or an endpoint being unable to use the A/V Edge Server. Correlation of such failures with individual networks, endpoints or A/V Edge Server can indicate potential deployment issues.

31
Call terminated on a mid-call media failure where one endpoint is of unknown type
The call was terminated after establishment due to a media timeout. The unknown endpoint is most likely a legacy client, legacy component or third party application. This failure can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

32
Call terminated on mid-call media failure where both endpoints are internal
The call was terminated after establishment due to a media timeout between the two internal endpoints. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks or endpoints can indicate potential deployment issues.

33
Call terminated on a mid-call media failure where one endpoint is internal and the other is remote
The call was terminated after establishment due to a media timeout between an internal endpoint and a remote endpoint. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

34
Call terminated on a mid-call media failure where both endpoints are remote
The call was terminated after establishment due to a media timeout between the two remote endpoints. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

35
Federated call terminated on a mid-call media failure where both endpoints are internal
The federated call was terminated after establishment due to a media timeout between the two internal endpoints. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

36
Federated call terminated on a mid-call media failure where one endpoint is internal and the other is remote
The federated call was terminated after establishment due to a media timeout between an internal endpoint and a remote endpoint. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

37
Federated call terminated on a mid-call media failure where both users are remote
The federated call was terminated after establishment due to a media timeout between two remote endpoints. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

38
Public service provider call terminated on a mid-call media failure with an internal endpoint
A public service provider call was terminated after establishment due to a media timeout between the external provider and an internal endpoint. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

39
Public service provider call terminated on a mid-call media failure with a remote endpoint
A public service provider call was terminated after establishment due to a media timeout between the external provider and a remote endpoint. This can be caused by a failure of one of the endpoints or a loss of network connectivity. Correlation of such failures with individual networks, endpoints or A/V Edge Servers can indicate potential deployment issues.

1000
Final handshake failed
Authentication failed for this user

1001
From URI not authorized to communicate with public IM providers
Could not add as a contact or reach the user because the destination URI belongs to a public IM provider and From user is not enabled for public cloud connectivity.

1002
From URI not authorized to communicate with federated partners
Could not add as a contact or reach the user or conference because the destination URI belongs to a domain outside of the organization and From user is not enabled for enterprise federation.

1003
User does not exist
Could not reach the user or conference because the destination URI did not exist in the enterprise or was incorrect.

1004
Route set is no longer valid
The destination user or conference is temporarily unreachable

1005
Cannot route to destination domain
Could not find a route to the destination user or conference domain outside of your organization

1006
Error routing on client connection
Cannot route to the destination user because his or her computer or other device is temporarily unreachable

1007
A legacy server was unable to route the message because a user or server is temporarily unreachable.
This diagnostic indicates that a legacy server could not route a message to the destination user or conference because a user or server is temporarily unreachable or offline.

1008
Unable to resolve DNS SRV record
Could not route to the destination user or conference domain because the DNS SRV query for the URI domain failed.

1009
No match for domain in DNS SRV results
Cannot route to the destination user or conference domain because the Lync Server Access Edge was unable to match the FQDN yielded by DNS SRV resolution with the URI domain.

1010
Certificate trust with another server could not be established
The Microsoft Lync Server was not able to establish an MTLS connection with another server because the peer server’s certificate did not pass verification by the operating system TLS provider.

1011
Ms-Diagnostics header not provided by previous hop
Ms-Diagnostics header is not provided by the previous hop. The previous hop may be a federated peer server, or an older version of Microsoft Lync Server such as Live Communications Server, or it is a client

1012
From URI is not authorized to communicate with users outside the enterprise
Could not add as a contact or reach the destination user or conference because user or conference URI belongs to a public IM provider or a domain outside of the organization and From user is not enabled for federation.

1013
Significant time skew detected during authentication
Attempt to authenticate failed because the Microsoft Lync Server machine clock is not synchronized with the domain controller.

1014
Unable to resolve host name record
Could not route to destination user or conference because the host name record of a peer server did not resolve.

1015
Cannot route from message source domain
Could not route to the destination user or conference outside of your organization because the From user URI domain was not configured in the Lync Server Access Edge internal domains list

1016
Message asserted domain traffic type does not match source domain
The Lync Server Access Edge was unable to route the message because the From user and asserted identity URI domains belong to partners of incompatible types

1017
Cannot route From and To domains in this combination
The Lync Server Access Edge was unable to route the message because the From and To user domains are not allowed in this combination.

1018
Parsing failure
Could not parse the message because one of its headers was invalid

1019
Referred-By header parameters are not valid
Could not validate the identity of the referrer because the sender was not authorized to use it or because one of the authorization parameters was invalid

1020
Identity of the referrer could not be verified with the ms-identity parameter
The cryptographic digest of the referrer identity is not valid within the context of the current call

1021
Integrity of the referrer information could not be verified with the ms-identity-cookie parameter
The cryptographic digest of referrer identity is not valid within the context of the current call

1022
Cannot process routing destination
Could not route the message because the destination address is not valid or because the sender is not trusted to provide explicit routing information

1023
The destination domain of the message resolved to a peer of an incompatible type
Could not route to the destination user or conference domain outside of our organization because the destination URI domain resolved to a server that was configured to represent partners of an incompatible type

1024
Message boss (on-behalf-of) domain traffic type does not match source domain
The Lync Server Access Edge was unable to route the message because the From user and boss (on-behalf-of) URI domains belong to partners of incompatible types

1025
Allowed partner domain resolved by DNS SRV to a FQDN that matches a different routing rule
Cannot route to the destination user or conference domain because the URI domain is configured in the Lync Server Access Edge as an allowed partner domain but DNS SRV resolution yielded a FQDN that matches a different routing rule.

1026
Domain resolved by DNS SRV to multiple FQDNs that match different routing rules
Cannot route to the destination user or conference domain because DNS SRV resolution with the URI domain yielded multiple FQDNs that match different routing rules in the Lync Server Access Edge.

1027
Cannot route this type of SIP request to or from federated partners
The following SIP requests cannot be routed to or from federated partners: REGISTER, SERVICE and get rich presence (polling SUBSCRIBE) requests.

1028
Domain resolved by DNS SRV to a configured hosting service but the domain is not in the allow list
Cannot route to the destination user or conference domain because the URI domain is not configured in the domain allow list.

1029
There is no configured route to process message destined to the enterprise edge.
Cannot route to the destination user or conference because there is no configured route to the enterprise edge.

1030
The destination in the edge route did not match any configured server and cannot be used for Request URI routing.
Cannot route to the destination user or conference because of incorrect information inserted by routing application.

1031
The server could not contact the authentication authority (DC).
The user could not be authenticated because the server failed to communicate with authentication authority (Directory Controller).

1032
Message diversion user domain traffic type does not match To user domain
The Lync Server Access Edge was unable to route the message because the To user and Diversion user URI domains belong to partners of incompatible types

1033
Previous hop server component did not report diagnostic information
The previous hop server did not insert an Ms-Diagnostics header into the response.

1034
Previous hop federated peer did not report diagnostic information
The federated peer did not insert an Ms-Diagnostics header into the response.

1035
Previous hop public IM provider did not report diagnostic information
The public IM provider did not insert an Ms-Diagnostics header into the response.

1036
Previous hop shared address space peer did not report diagnostic information
The shared address space federated peer did not insert an Ms-Diagnostics header into the response.

1037
Previous hop client did not report diagnostic information
The client did not insert an Ms-Client-Diagnostics header into the response.

1038
Failed to connect to a peer server
Cannot route to the destination user or conference due to a failure to connect to a peer server. Administrators should check the diagnostic header sent with this code for more information about the ‘Source’, ‘Peer’, ‘Port’ and other failure details, if available.

1039
Failed to complete TLS negotiation with a peer server
Cannot route to the destination user or conference because TLS negotiation with a peer server failed

1040
Connection to a peer server failed
Cannot route to the destination user or conference because the connection to a peer server failed

1041
Peer server pool is out of service
Cannot route to the destination user or conference because all servers in a peer server pool are out of service

1042
Failed to connect to the local edge server
Cannot route to the destination user or conference due to a failure to connect to the local edge server

1043
Failed to complete TLS negotiation with the local edge server
Cannot route to the destination user or conference because TLS negotiation with the internal edge of the local edge server failed

1044
Connection to the local edge server failed
Cannot route to the destination user or conference because the connection to the local edge server failed

1045
Local edge server pool is out of service
Cannot route to the destination user or conference because all servers in the local edge server pool are out of service

1046
Failed to connect to a federated peer server
Cannot route to the destination user or conference due to a failure to connect to a federated peer server

1047
Failed to complete TLS negotiation with a federated peer server
Cannot route to the destination user or conference because TLS negotiation with a federated peer server failed

1048
Connection to a federated peer server failed
Cannot route to the destination user or conference because the connection to a federated peer server failed

1049
Federated peer server pool is out of service
Cannot route to the destination user or conference because all servers in a federated peer’s edge server pool are out of service

1050
Failed to connect to a public IM provider
Cannot route to the destination user or conference due to a failure to connect to a public IM provider

1051
Failed to complete TLS negotiation with a public IM provider
Cannot route to the destination user or conference because TLS negotiation with a public IM provider failed

1052
Connection to a public IM provider failed
Cannot route to the destination user or conference because the connection to a public IM provider failed

1053
Public IM provider is out of service
Cannot route to the destination user or conference because all servers in a public IM provider are out of service

1054
Failed to connect to a shared address space federated peer server
Cannot route to the destination user or conference due to a failure to connect to a shared address space federated peer server

1055
Failed to complete TLS negotiation with a shared address space federated peer server
Cannot route to the destination user or conference because the connection to a shared address space federated peer server failed

1056
Connection to a shared address space federated peer server failed
Cannot route to the destination user or conference because the connection to a shared address space federated peer server failed

1057
Shared address space federated peer is out of service
Cannot route to the destination user or conference because all servers in a shared address space provider’s edge server pool are out of service

1058
An error occurred routing on the remote client connection
The message could not be routed to the destination remote user because his or her computer or other device is temporarily unreachable

1059
Cannot route anonymous user to or from federated partner
Anonymous users cannot be routed to or from outside of your organization

1060
Remote user client access is disabled
Message from remote user client cannot be routed because access for remote user clients is disabled

1061
Anonymous user client access is disabled
Message from anonymous user client cannot be routed because access for anonymous users is disabled

1063
Cannot route to blocked IM Service Provider
Could not route the message because the domain resolved by DNS SRV to a server that is a blocked IM Service Provider

1064
Cannot route to blocked domain
Could not route the message because the domain is in the list of blocked (denied) domains

1065
Federation is disabled
Could not route the message because all federation is disabled on the Lync Server Access Edge

1066
Shared address space routing is disabled
Could not route to the destination user or conference hosted at another deployment in your organization because shared address space (cross-premise) routing is disabled on the Lync Server Access Edge

1067
Unacceptable status code present in response from untrusted source
An untrusted source sent a response with an unacceptable status code. The status code has been changed to 500.

1068
Port is configured for health monitoring only
The port on which the message was received is configured for health monitoring and cannot accept messages

1071
Error in shared address space configuration caused a routing loop at the local deployment edge
Could not route the message because an error in the shared address space (cross-premise) configuration caused the message to loop back at the local Lync Server Access Edge

1072
User not homed in this forest
Could not route the message received from another forest because the target user is not homed in this forest

1073
Identity of the referred user (referee) could not be verified
The cryptographic digest of the referrer identity is not valid within the context of the current call

1074
Domain not hosted by this service
Could not reach the user or conference because the domain of the destination URI is not hosted by this service.

1076
Protocol Stack Telemetry data
This diag code is reserved for protocol stack telemetry data, it is reported directly to CER and not sent out on the wire.

2000
Prompted subscriber does not exist

2001
Contact does not exist

2002
Group does not exist

2003
Category publication failed – Cannot overwrite read only publication

2004
Subscriber is not authoried to subscribe

2005
The user in the FROM uri is not found

2006
Container member limit exceeded

2007
Contact limit exceeded

2008
Group limit exceeded

2009
Contact extension too large

2010
Category size limit exceeded

2011
Delivery context per subscriber limit exceeded

2012
Category subscription limit exceeded

2013
msrtc-event-categories extension required

2014
Subscription dialog does not exist

2015
Duplicate group name

2016
New subscription is required

2017
Invalid request due to endpoint not being registered

2018
com.microsoft.msrtc.presence extension required

2019
Report error service is not available

2020
Request Uri not equal to To Uri

2021
Missing GRUU endpoint

2022
Contact: * must only be used when Expires

2023
Missing +sip.instance in contact

2024
Badly formed +sip.instance in contact

2025
Mismatched +sip.instance and epid identifiers

2026
Error while parsing subscribe body

2027
The Uri is a GRUU for valid server role but version is too low

2028
GetNormalizedResponseExpires failed

2029
Permission does not exist

2030
Invalid Permission

2031
Non Zero expires value or ToTag present for a polling subscribe

2032
Category publication failed – Category name is not registered

2033
Aggregation request contains invalid data

2034
Subscribe presence verification failed

2035
Directory search auth denied

2036
Presence change auth denied

2037
ACL change auth denied

2038
BatchSubscribe cannot have To and From different

2039
Contact change auth denied

2040
Containers change auth denied

2041
Subscribers change auth denied

2042
Service auth denied

2043
Rejecting third party registration

2044
Publication version out of date

2045
Container version out of date

2046
Contact version out of date

2047
Permission version out of date

2048
Duplicate instance specified

2049
Duplicate container specified

2050
Permission limit exceeded

2051
User search filter limit exceeded

2052
Presence document too large

2053
User info document too large

2054
Server GRUU allowed only for msrtc-event-categories subscribe

2055
Proxy-Require not supported

2056
adhoclist not supported for this event

2057
GRUU registration required because user is in rich mode

2058
msrtc-event-categories subscription not allowed for this target uri

2059
Max subs per user limit reached

2060
Add/Delete operation not supported without Create

2061
Subscribe refresh attempted without existing dialog

2062
Dialog exists for another endpoint

2063
SetPresence is not allowed without registration

2064
adhoclist is not supported with out Supported: eventlist

2065
Batch Subscribe is not allowed without registration

2066
Batch Subscribe is not allowed without cached registration

2067
Legacy operation not allowed

2068
Legacy provisioning subscription is not allowed for UC enabled users

2069
Internal Error: ProcessSubscribe failed

2070
Internal Error: CheckRequireHeaders failed

2071
Internal Error: ProcessRegister failed

2072
Internal Error: Failed to serialize route info

2073
Internal Error: Failed to execute registration sproc

2074
Internal Error: Register ValidateAndPreprocessRequest failed

2075
Internal Error: Register request processing failed

2076
Internal Error: Failed to execute deregistration sproc

2077
Internal Error: Failed to read AuthorizationReader rowset

2078
Internal Error: GetAggregateState Failed

2079
Internal Error: GenerateMsrtcPresenceDocFromTemplate failed

2080
Internal Error: CreateUserPresenceDocument failed

2081
Internal Error: Error creating SOAP document

2082
Internal Error: Failed to process service request

2083
Internal Error: Failed to process register request

2084
Internal Error: Unable to retrieve Action from sproc rowet

2085
Internal Error: ProcessAggregationInitial failed

2086
Internal Error: Unable to generate self categories document

2087
Internal Error: SerializePublish Data failed

2088
Internal Error: ActionContactInfoReader rowset reading failed

2089
Internal Error: GenerateRLMIDocument failed

2090
Internal Error: CreateAndSetRLMIDocRootProperties failed

2091
Internal Error: GetBatchSubChildResult failed

2092
Internal Error: AddRLMIResourceEntry failed

2093
Internal Error: GenerateAndSendWPendingDocument failed

2094
Internal Error: GenerateAndSendPromptedSubscriberList failed

2095
Internal Error: GetUserInfo for presence failed

2096
Internal Error: GetAggregateState for presence failed

2097
Internal Error: GenerateBSubMIME failed

2098
Internal Error: SubscribePresenceResultReader rowset reading failed

2099
Internal Error: ParseLegacyInteropState failed

2100
Internal Error: GenerateCpimPresenceDoc failed

2101
Internal Error: SubscribePendingPresenceResultReader rowset reading failed

2102
Internal Error: CreateWPendingDocument failed

2103
Internal Error: SubscribePermissionResultReader rowset reading failed

2104
Internal Error: CreateFullACLsDocument Failed

2105
Internal Error: GetSubscribeSelfResult rowset reading failed

2106
Internal Error: UpdateRpSubscriptionTable failed

2107
Internal Error: CreateRoamingDataDocument Failed

2108
Internal Error: SubscribeContactResultReader rowset reading failed

2109
Internal Error: CreateFullContactsDocument Failed

2110
Internal Error: SubscribeProvisioningResultReader rowset reading failed

2111
Internal Error: CreateProvisioningDocument Failed

2112
Internal Error: TryFormatPolicy failed

2113
Internal Error: FormatProvisioningGroup failed

2114
Internal Error: Could not extract the fixed pool properties

2115
Internal Error: Substitution for SIP App Uri list failed

2116
Internal Error: Provisioning GenerateEndElement failed

2117
Internal Error: Legacy subscription was called as a result of a rich subscription and it failed

2118
Internal Error: GenerateCategoriesDocument failed

2119
Internal Error: RpSubscribeResultReader rowset reading failed

2120
Internal Error: DeleteRpSubscriptionTableEntry Failed

2121
Internal Error: Adding the RLMI doc failed

2122
Internal Error: AppendCategoriesDoc failed

2123
Internal Error: Closing Mime doc failed

2124
Directory search data server down

2125
Directory search connect error

2126
Directory search operation cancelled

2127
Directory server busy

2128
Publisher lock request failed

2129
Publisher lock request timedout

2130
Publisher lock request cancelled

2131
Publisher lock request deadlocked

2132
Publisher computation lock is currently held by someone else

2133
GetPresence functionality disabled

2134
Active directory operation timed out

2135
Aggregation request timed out

2136
Aggregation request failed

2137
Error report too large

2138
Publication data too large

2139
Terminating old subscription since new subscription dialog took over the previous one

2140
The specified delegate relation does not exist

2141
Delegate version is out of date

2142
Operation is not authorized for this delegate

2143
Delegate operation is invalid

2144
User bound publication requires at least one endpoint

2145
Delegate limit exceeded

2146
Server handling the subscription is not reachable via RPC.

2147
Directory search is disabled.

2150
MWINotify must have the same SIP URI in the To, From headers and in the Message-Account field

2151
Internal Error: Failed to process notify request

2152
Internal Error: Registration sproc did not return any result

2153
Internal Error: REGISTER received on a cluster that is neither the primary nor the backup.

2154
Internal Error: Error creating Registration response.

2155
Internal Error: Failed to add contact header to Registration response.

2156
SingleSubscribe cannot have server GRUU in the To URI

2157
Source network is not set for a single subscribe request when tenant ids of the To and From users are different.

2158
Source verification level is unverified and the subscriber is not explicitly on the contact list of the publisher.

2159
Internal Error: The server was not found in the known server table. It is possible that the DB and stack are out of sync.

2160
Internal Error: GetInternalServerInfo failed.

2161
Internal Error: GetInternalServerInfo succeeded but pool GRUU is empty.

2162
Rich presence notification is throttled and the subscription dialog has been terminated as the outstanding notify count per dialog exceeded the maximum limit.

2163
Ucs policy processing failed.

2164
Contact list is read only as the contact list is being migrated or has migrated to Exchange.

2165
Contact subscription is not allowed as the user’s contact list has migrated to Exchange.

2166
Internal Error: Subscribe processing failed

2167
Internal Error: Failed to send contacts subscription http request

2168
Internal Error: Failed to process contacts subscription http response

2169
Internal Error: Contact Subscription to Exchange failed with unknown error

2170
Contact Subscription to Exchange failed with invalid user info error

2171
Internal Error: Contact Subscription to Exchange failed with malformed request error

2172
Contact Subscription to Exchange failed as the subscription response from Exchange was malformed

2173
Contact Subscription to Exchange failed with account disabled error

2174
Contact Subscription to Exchange failed with access denied error

2175
Contact Subscription to Exchange failed with invalid mailbox version error

2176
Internal Error: Contact Subscription to Exchange failed with connection error

2177
Contact Subscription to Exchange failed with invalid smtp address error

2178
Contact Subscription to Exchange failed with invalid mailbox error

2179
Contact Subscription to Exchange failed as the mailbox failover was in progress

2180
Contact Subscription to Exchange failed as the mailbox move was in progress

2181
Internal Error: Contacts subscription http request failed

2182
Internal Error: Contacts subscription http request timed out

2183
Internal Error: Failed to create contact list packed table during contact subscription

2184
Group count in contact list received from Exchange for the user exceeded the server supported maximum

2185
Contact count in contact list received from Exchange for the user exceeded the server supported maximum

2186
Contact subscription has been terminated as the user migrated to ucs mode.

2187
Specified REGISTER dialog does not exist, Rejecting with 481

2188
The request is missing the SIP-If-Match header

2189
The request contains an invalid SIP-If-Match header

2190
3PP publish body parse failure

2191
Internal Error: Failed to process publish response

2192
3PP publish must have the same SIP URI in the To, Request Uri headers and in the Entity field in the body. The From URI must be same as the To URI or must belong to a valid provider domain and the user portions much match

2193
Internal Error: Failed to process publish request

2194
Request and To URIs must match for dialog creating subscribe requests targeting phone SIP URIs

2195
Server is busy – Request rejected by presence polling throttling mechanism

2196
Internal Error: Failed to verify 3PP request

2197
3PP federated subscribe with a phone number in the From SIP URI must have a matching To URI or the From URI must belong to a valid presence provider domain and the user portions of the From and To URIs much match

2198
Contact Subscription to Exchange failed with a service request error. Possible exchange configuration issue.

2199
Contact Subscription to Exchange failed with an unknown error while trying to create a subscription on Exchange

2200
Contact Subscription to Exchange failed with an unknown error. EndAddSubscription failed.

2201
Contact Unsubscription from Exchange failed with a service request error. Possible exchange configuration issue.

2202
Contact Unsubscription from Exchange failed with an unknown error

2203
Contact subscription to Exchange failed with an autodiscover error

2204
Ucs contact migration to Exchange failed with an autodiscover error

2205
Contact subscription to Exchange failed with an oauth error

2206
Contact subscription to Exchange failed with an unsupported store error

2207
Contact subscription to Exchange failed with an store config error

2208
Ucs Contact Subscription CER data
This diag code is reserved for Ucs contact subscription CER data, it is reported directly to CER and not sent out on the wire.

2209
This user has too many endpoint entries, which can happen if endpoints do not unregister properly.

2210
Internal Error: Contact notification from Exchange failed with unknown error

2211
Contact notification from Exchange failed as the GetImItemList response from Exchange was malformed

2212
Contact notification from Exchange failed with account disabled error

2213
Contact notification from Exchange failed with invalid mailbox version error

2214
Internal Error: Contact notification from Exchange failed with connection error

2215
Contact notification from Exchange failed with invalid smtp address error

2216
Contact notification from Exchange failed with invalid mailbox error

2217
Contact notification from Exchange failed as the mailbox failover was in progress

2218
Contact notification from Exchange failed as the mailbox move was in progress

2219
Contact notification from Exchange failed with an autodiscover error

2220
Contact notification from Exchange failed with an oauth error

2221
Contact notification from Exchange failed with an unsupported store error

2222
Contact notification from Exchange failed with an store config error

2223
Contact notification from Exchange failed while generating the contact list

2224
Ucs Contact Notification CER data
This diag code is reserved for Ucs contact notification CER data, it is reported directly to CER and not sent out on the wire.

3000
Bad From in C3P Request

3001
Bad To in C3P Request

3002
Invalid Target User

3003
The conference-entity supplied in the C3P request is invalid

3004
The requested C3P command is not implemented

3005
The request cannot target a MCU

3006
Failed to parse the C3P request

3007
AddUser C3P blob invalid

3008
Access Method or Auth Method in C3P request is not acceptable

3009
Malformed endpoint entity

3010
Bad request without Session-Timer extension

3011
Failed to process Ms-Mcu-Contact header

3012
Invalid Conf Uri

3013
Invalid Mcu Uri

3014
Failed authorization

3015
This meeting does not allow 3rd-party dial-out by attendees

3016
The supplied role is invalid

3017
Unknown presenter dial-out by attendees is not allowed

3018
One or more joining methods are invalid. Exactly one method may be specified

3019
Forbidden destination for anonymous user

3020
Anonymous user targeting non-focus or non-mcu conference URI

3021
The destination is not conf URI, anonymous users are not authorized

3022
Anonymous user targetting server without focus

3023
Anonymous user unAuthorized

3024
Anonymous user failed to authorize

3025
Anonymous user not authorized

3026
Conference doesnt allow anonymous users

3027
User not allowed in closed conference

3028
Anonymous access disabled globally

3029
Anonymous user trying to establish SA multiple times

3030
GetConferenceKeyHash failed

3031
GetConferenceKeyHash timeout

3032
Conference does not exist
The user is attempting to join an unknown conference.  This typically occurs when a user attempts to join via a conference link in an old meeting request or by user error when copy-pasting an incomplete link from a meeting request.

3033
The C3P transaction timed-out
This error indicates that the conferencing server did not receive an appropriate response to a request it sent.  This will occur due to server or network performance issues, or due to a product defect.  Administrators should look for overloaded Microsoft Communications server components or network issues.

3034
Request received with no prior INVITE join Dialog

3035
BYE without To Tag; dialog that does not exist, Rejecting with 481

3036
Subscribe refresh for unknown dialog

3037
Conference dialog does not exist

3038
Info request received for unknown dialog – no To Tag

3039
Update request received for unknown dialog

3040
Conference is not active
The user was removed from the conference because the conference was deleted.  This error typically occurs when a user is performing an action, such as joining the A/V Conferencing Server, when the conference is deleted.

3041
Participant is not connected to conference
Indicates that the participant is attempting to send a command or join an MCU without being connected to the conference.

3042
Focus dialog is not active
In response to an INVITE, this means that the participant is connected to one or more MCUs but does not have an active focus dialog. Focus dialogs are required to send INVITE to an MCU. In the context of a SUBSCRIBE, this indicates that the participant does not have a focus dialog, but makes no indication with regard to MCU dialogs.

3043
The organizer policy is not configured or is invalid

3044
Anonymous access is not allowed

3045
The supplied media-type is invalid

3046
MCU does not support dial-in via SIP INVITE.

3047
User already authorized. Operation not allowed

3048
Internal Error: The response received from the MCU was unparseable

3049
Internal Error: SerializeDialogID failed

3050
Internal Error: Conf Leave Sproc failed

3051
Internal Error: IsKeepAliveEnabled Call failed

3052
Internal Error: GetContentString failed

3053
Internal Error: SerializeDialogContext failed

3054
Internal Error: Failed to prepare for stateful processing

3055
Internal Error: ConfJoinSproc failed

3056
Internal Error: Failed to process join activation result

3057
Internal Error: ConfJoinResultReader failed

3058
Internal Error: GetConfLeaveResultReader failed

3059
Internal Error: ConstructConfUri failed

3060
Internal Error: Failed to schedule ConfMessageDispatcherSproc

3061
Internal Error: Failed to get preprocess result rowset

3062
Internal Error: getMcu failed

3063
Internal Error: Send AddUser Command failed

3064
Internal Error: Invalid MCU Contact Information received

3065
Internal Error: ConfSubSproc failed

3066
Internal Error: ConfSubscribeResultReader Failed

3067
Internal Error: GenerateConferenceRosterDoc Failed

3068
Internal Error: Subscribe Rowset ActionReader Failed

3069
Internal Error: ConfUpdateParticipant sproc failed

3070
Internal Error: GetAuthenticationInfo failed

3071
Internal Error: Cached Confuri not found in anonymous user SA

3072
Internal Error: Anonymous user challenge failed

3073
Internal Error: VerifyConfDigestCredentials failed

3074
Internal Error while handling conferencing requests

3075
Internal Error: InitializeParams for ConfInfoContext failed

3076
Internal Error: Failed to generate C3P response

3077
Internal Error: IntializeParams for ConfInvite failed

3078
Internal Error: ProcessConfJoinInvite failed

3079
Internal Error: ProcessConfMediaInvite failed

3080
AddUser operation failed
The conferencing server sends this diagnostic to indicate that an MCU rejected an addUser request.  This could be a normal behavior when the server rejects a request because another one is still pending.

3081
Internal Error: Failed to Construct CallInfo header

3082
Internal Error: ForwardRequestStatefully failed

3083
Internal Error: Anonymous AuthorizeAndDispatch failed

3084
Internal Error: Anonymous Authorize failed

3085
Internal Error: InitializeParams for ConfServiceContext failed

3086
Internal Error: Failed to construct C3P error response

3087
Internal Error: Failed to get cert info

3088
Internal Error: ProcessConfSubscribe failed

3089
Internal Error: IntializeParams for ConfSubscribe failed

3090
Internal Error: InitializeParams for ConfUpdate failed

3091
Internal Error: ProcessConfUpdate failed

3092
Internal Error: ConfQueryKeySproc failed

3093
Internal Error: Query Conference Key rowset not found

3094
Internal Error: GetKeyHashFromRemoteFocus failed

3095
Internal Error: ComputeUserCredHash failed

3096
Focus Logic not implemented

3097
No MCU is available via the MCU factory

3098
No MCU Factory Available

3099
The requested media is not configured for this conference.

3100
Maximum participant count for this meeting has been exceeded.

3101
Batching is not supported

3102
Invalid MCU information supplied

3103
Invalid endpoint count in the message

3104
The requested command requires that target user must be different from the source

3105
The target user is not active and hence the requested command cannot be completed

3106
The C3P message is parsable but it has one or more invalid elements or attributes that are not allowed in this context

3107
C3P Internal Error

3108
MCU is unreachable

3109
The request was sent to the MCU but the C3P transaction timed out

3110
The MCU rejected addConference request. This usually indicates a mis-configuration.

3111
MCU allocation is in progress. The request needs to be retried

3112
From user is not authorized to use this focus factory

3113
Conference Terminated – Deleted
The user was removed from the conference because the conference was deleted.  This can occur when an organizer deletes a conference using the Outlook conferencing add-in or by using a third party application built upon UCMA while users are connected to the conference.

3114
Conference Terminated – Enterprise User Absent
A PSTN conferencing user or anonymous user was removed from a conference because the conference had only federated or anonymous users for 90 minutes (default). The timeout duration is an Administrator configurable server setting.

3115
Conference Terminated – Inactivity
The user has been removed because the conference has been running longer than 24 hours (default) and no new users have joined.  This typically occurs when a user goes home without leaving the conference.  The timeout duration can be configured by an administrator.

3116
Conference Terminated – Organizer Ended Session
The user has been removed from a conference which was ended by the organizer.  This is normal behavior.

3117
Conference Terminated – Organizer Was Taken Offline

3118
Participant Removed
The user has been ejected from the conference by the organizer.  This is normal behavior.

3119
Participant Denied

3120
Participant session expired
The user has been removed from the conference because the client failed to send a keep alive message.  This can commonly occur due to network drops, such as a lost wireless connection, or if the user’s laptop goes into hibernation mode.  This primarily affects remote users and cross-pool conference joins.

3121
The supplied media-type is not provisioned for the conference

3122
The C3P request sent to the MCU failed

3123
Previous Subscription dialog being terminated

3124
Subscription dialog being terminated – Meeting Size Exceeded

3125
Conference has expired and hence cannot be activated

3126
Unauthorized – The user does not have the privilege for the requested operation

3127
An operation that violates the Trusted User Policy was attempted

3128
Invalid session-on-behalf-of entity

3129
Failed to process P-Session-On-Behalf-Of header

3130
Failed to validate the contact header

3131
Internal Error: ConfPreprocessForForDispatchToMcu sproc failed

3132
Internal Error: DeSerializeDialogContext failed

3133
Internal Error: Failed to retrieve the results of PreprocessForDispatchToMcu

3134
Invalid Certificate in the request.

3135
Referred in C3P request is not acceptable in the current context.

3136
Failed to route request to the Mcu

3137
Mcu has not published a routable SIP URI

3138
The requested conference subject exceeds the maximum length.

3139
There are no active conference directories assigned to this pool.

3140
Failed allocating PSTN meeting id.

3141
Could not find a conference directory to match the given id.
The conference ID entered by a PSTN conferencing user is parseable but the conference directory indicated by the ID does not exist.  This typically occurs if a user mistypes the conference ID, but may also indicate that a conference directory was mistakenly deleted while user were still using conferences resolved by it.

3142
The id could not be matched to a unique conference directory. This is a server configuration error.

3143
Timeout connecting to authoritative conference directory server.

3144
Failure connecting to authoritative conference directory server.

3145
Deprecated – The meeting id was invalid and could not be decoded.
A PSTN conferencing user failed to join a conference homed on a legacy server because the conferencing ID entered could not be resolved.  The most common reason is user error when entering the ID.  The conferencing attendant will typically allow the user to try again up to three times.

3146
Failed to call resolve conference sproc.

3147
Delegate Request – C3P From is not equal to the session-on-behalf-of header.

3148
Delegate Request – C3P From is not equal to the SIP To header.

3149
The requested C3P command is not allowed in second-person context.

3150
Second-person request dialog must have trusted privilege asserted.

3151
Failed fetching meeting policy.

3152
Client version blocked by conference focus.
This indicates that a legacy conferencing server rejected a conference join because the client version has been blocked.  This was specifically implemented for a critical update to legacy servers to block certain Live Meeting clients which joined the Focus directly.  This error is not used by new releases as the client version filter checks all supported clients.

3153
The command used automatic user presenter classes not supported by this server.

3154
Lobby bypass for phone users is not supported by this server.

3155
The scheduling operation would exceed the user’s quota of static meetings.

3156
The indicated meeting is a static meeting, but the request was for non-static.

3157
The indicated meeting is a non-static meeting, but the request was for static.

3158
This request does not match the expectated form for a static meeting.

3159
The requested modification is not valid on a static meeting.

3160
This endpoint is not allowed to request PSTN join semantics.

3161
Static meetings are not permitted.

3162
Lobby join for a participant has been rejected because lobby quota limit for non-enterprise users was reached.

3163
The meeting id to resolve is too short.
The conference ID entered by a PSTN conferencing user was shorter than expected.  This most commonly occurs when a user pauses when entering the ID.  The conferencing application interprets this pause as the user is done typing.  This error can also occur if a user mistypes a number.

3164
The meeting id to resolve is too long.

3165
The meeting id to resolve has an incorrect auth length component.

3166
The meeting id to resolve contains non-digit characters.

3167
The meeting id to resolve begins with zero.

3168
The meeting id to resolve contains non-digit characters after descrambling.

3169
The meeting id to resolve has unneccessary padding on the id component.
The conference ID entered by a PSTN conferencing user is invalid.  This typically occurs when a user mistypes the conference ID.

3170
The meeting id to resolve does not have the expected check digit.
This occurs when validation of a conference ID entered by a PSTN conferencing user fails.  The most common cause is a user mistyping a conference ID.

3171
Failed computing check digit for the meeting id.

3172
There was no meeting id given to resolve.

3173
Conference directory home pool inconsistency.

3174
An authoritative conference directory was found, but the given id is not currently assigned.
The conference ID entered by a PSTN conferencing user is parseable but does not match any known conference.  This typically occurs if a user mistypes the conference ID.  This may also occur if the user is entering a conference ID from an old meeting request.

3175
The specified operation is not valid for a participant in the lobby.

3176
The endpoint was removed to make room for another endpoint for the same user.

3177
The endpoint disconnected.

3178
Unsupported modification of the server mode attribute of the conference.

3179
Unsupported value for server mode attribute of the conference.

3180
Recording is not allowed

3181
Rich join is not allowed for lobby bypassed user.
PSTN endpoints can bypass the conference lobby if the lobby bypass feature is enabled for a conference. Due to architectural limitations, joining a rich client at the same time would result in the user having access to data without being admitted, so it is unsupported.

3182
Empty request ID.

3183
Incorrect conference key.
This error could occur when a user enters an invalid PIN.

3184
Malformed conference key.

3185
Not a front end server.
Issuing server is not a front end server

3186
Invite dialog terminated since new dialog replaced it
The existing dialog is terminated because a new dialog from the same endpoint replaced it

3187
Conference Terminated – Server is under maintenance
This user is either failing over or failing back to another server and conferencing services are unavailable during this time

3188
This user is not permitted to endorse requested endorsee
This user is likely not in the same trust boundary as the requested endorsee

3189
The requested entity cannot be endorsed.
This server does not permit endorsing for the requested endorsee.

3190
The requested entity is not permitted to endorse.
This server does not permit endorsing by the requesting user.

3191
Internal Error: ConfEndorseSproc failed

3192
Internal Error: ConfEndorseSproc failed for an unknown reason

3193
Could not find a front end server that owns the given pstn meetind id.
The conference ID entered by a PSTN conferencing user is parseable but the primary front end server that owns the conference ID is not reachable.

3194
A Quorum of Servers is not available to commit this operation.
Unexpected failure on replication to secondary front end servers.

3195
Conferencing Join Telemetry data.
This diag code is reserved for conferencing join time telemetry data, it is reported directly to CER and not sent out on the wire.

3196
Failed Fetching Meeting Id.
Encountered unexpected failure while trying to fetch PSTN meeting ID from MCU factory.

3197
Conferencing PSTN Meeting ID deletion.
This diag code is reserved for conferencing PSTN meeting ID deletion, it is reported directly to CER and not sent out on the wire.

3198
Conference creation report.
This diag code is reserved for reporting creation of a conference, it is reported directly to CER and not sent out on the wire.

3199
Conference deletion report.
This diag code is reserved for reporting deletion of a conference, it is reported directly to CER and not sent out on the wire.

3200
Conference expiration report.
This diag code is reserved for reporting a conference expiration, it is reported directly to CER and not sent out on the wire.

3203
Conference modify report.
This diag code is reserved for reporting modification of a conference, it is reported directly to CER and not sent out on the wire.

4000
User services default

4001
XML parse failure

4002
Multiple users associated with the source phone number

4003
From URI not enabled for remote access

4004
Credentials provided are not authorized to act as specified from URI

4005
Destination URI either not enabled for SIP or does not exist

4006
User not found in pool

4007
Resource is unknown in this deployment

4008
Input data too large – One of the paramaters to the sproc exceeds limit

4009
Multiple users associated with the destination phone number

4010
Missing endpoint identifier

4011
Epid Not Present

4012
EPID too long

4013
Content-type does not match the expected content-type

4014
Content-type is not present

4015
Missing or badly formed instance information in GRUU

4016
Missing event header

4017
AOR in GRUU is not owned by the message source

4018
No Contact header present.

4019
Multiple event header present

4020
Invalid ToTag received

4021
Body is Empty

4022
GetBody failed

4023
GetAcceptID failed

4024
Invalid To Url

4025
Invalid DisplayName

4026
Could not get the event header

4027
RequestUri contains a non-blank user name

4028
Multiple user-agent header present

4029
A header is present multiple times which is not allowed

4030
Multiple require headers not supported

4031
Error trying to get Min-SE header

4032
Error trying to get Session-Expires header.

4033
To User not authorized for Federation

4034
To User not authorized for public cloud access

4035
Phone identity is not authorized – associated user entity not found in DB

4036
SIP enabled entity is not found in DB

4037
AuthorizeUser for SIP or phone identity failed

4038
AuthorizeIdentities for SIP or phone identity failed

4039
User does not have any routable endpoints

4040
Not Acceptable — Unknown MIME type in Accept header

4041
Dialog Id conflict

4042
Input data too large – DB column length violation

4043
DB Type Conversion error

4044
DB Column Conversion overflow

4045
Invalid Require header

4046
Invalid combination of require headers present

4047
Unknown Require header

4048
Expires value too small

4049
Target is either disabled or moving away

4050
From User is either disabled or moving away

4051
Endpoint is not registered

4052
Cached route does not match

4053
Too many contact headers.

4054
Min-SE value is too high.

4055
Bad Event

4056
Internal Error: IsTokenPresentInHeader call failed

4057
Database stored procedure failed to execute properly
This diagnostic indicates a problem occurred with the backend database. The server was unable to process a request because a database stored procedure did not execute successfully. The diagnostic header reported with this code should indicate which server generated the error. Administrators should check the database for possible network or capacity issues, if the error did not correspond with a known maintenance period.

4058
Internal Error: Failed to check the authorization flags – GetAuthenticationInfo failed

4059
Internal Error: DbStore Authorization sproc failed

4060
Internal Error: Failed to check the authorization flags –  IsAuthorized failed

4061
Internal Error: Internal server error when processing Subscription request

4062
Internal Error: Failed to check the authorization flags –  FillAuthenticationInfo failed

4063
Internal Error: Failed to get GetExternalSource

4064
Internal Error: Failed to get GetSourceNetwork

4065
Internal Error: Failed to get auth protocol

4066
Internal Error: Failed to attach routing context

4067
Internal Error: Failed to get auth user identity

4068
Internal Error: Failed to get identity authorization requirements

4069
Internal Error: Failed to get asserted identity string

4070
Internal Error: Failed to queue an authorization message

4071
Internal Error: MessageDispatcher failed.

4072
Internal Error: Failed to get the home server.

4073
Internal Error: UnExpected External Source

4074
Internal Error: Failed to generate the challenge

4075
Internal Error: Failed to check the destination path

4076
Internal Error: Failed to check for FROM server role

4077
Internal Error: Failed to do route set optimization failed

4078
Internal Error: Failed to get the sender info

4079
Internal Error: Failed to get the From header information

4080
Internal Error: Failed to get the P-Asserted-Identity header

4081
Internal Error: Failed to get the To header information

4082
Internal Error: Failed to get TO uri string

4083
Internal Error: Failed to initialize FROM TO information.

4084
Internal Error: Failed to select request target

4085
Internal Error: Failed to determine if request URI is phone

4086
Internal Error: Failure while checking options responseRequired.

4087
Internal Error: Identity AOR and From header don’t match

4088
Internal Error: Failed to set the Request URI.

4089
Internal Error: Failed to check for TO server role

4090
Internal Error: Failed to get request URI

4091
Internal Error: Failed to get user@host from GRUU.

4092
Internal Error: Failed to queue a message dispatcher request

4093
Internal Error: GetCachedEndpointInfo failed

4094
Internal Error: ResolveGRUUFromRoute failed.

4095
Internal Error: Failed to set display name in from header.

4096
Internal Error: Failed to set display name in P-Asserted-Identity header.

4097
Internal Error: Failed to Restore Contact Entry.

4098
Internal Error: Failed to set user data.

4099
Internal Error: Failed to validate GRUU contacts

4100
Internal Error: Failed to find FQDN in route set.

4101
Internal Error: Failed to resolve ES GRUU

4102
Internal Error: Malformed server GRUU

4103
Internal Error: Failed to determine server peer name

4104
Internal Error: Failed to determine if internal peer is an FE.

4105
Internal Error: Failed to get Call-Id

4106
Internal Error: Failed to get From Tag

4107
Internal Error: Failed to get To Tag

4108
Internal Error: Error trying to get Supported header

4109
Internal Error: Failed to get content-type header

4110
Internal Error: GetExpiryTimes failed

4111
Internal Error: GenerateRandomTag failed.

4112
Internal Error: Failed to get displayname

4113
Internal Error: XML generation failed

4114
Internal Error: Out of Memory

4115
Internal Error: GetGenericParameter failed

4116
Internal Error: GetUserAtHost failed

4117
Internal Error: SetDestinationInRequestURI failed

4118
Internal Error: AttachEndpointRoutingContextIfNeeded Failed

4119
Internal Error: GetEndpointRoute Sproc failed

4120
Internal Error: IntializeParameters failed

4121
Internal Error: GetQueryResourceAuthorizationInfo failed

4122
Internal Error: XML construction failed

4123
Internal Error: Failed to convert to UNICODE

4124
Internal Error: Error executing sproc – execution failure

4125
Internal Error: Error executing sproc – native failure

4126
Internal Error: GetEndpointThrottlingContext failed

4127
Service Unavailable — Functionality not implemented

4128
GetEndpointRouteComplete failed

4129
Service Unavailable — Too many outstanding requests in Pool

4130
Server is busy.

4131
Server is busy – Request rejected by db queue throttling mechanism

4132
Server is busy – Request rejected by endpoint throttling mechanism

4133
SQL deadlock encountered

4134
Database operation timeout. This can happen due to too many requests that require database interaction

4135
Internal Error: Failed to process incoming App Via Header

4136
Internal Error: Failed to commit outgoing App Via Header

4137
Supported headers parse failure

4138
C3Pversion of the request is unsupported

4139
Internal Error: Initializing the batched polling subscribe request failed

4140
User logged out

4141
User disabled

4142
User moved

4143
Bad Phone Number

4144
Database communication link is down
The server was unable to process a request because the backend database is unavailable. The diagnostic header reported with this code should indicate which server generated this error. Administrators should check the database for possible networking or capacity issues, if this failure did not correspond with a known maintenance period.

4145
Internal Error: Failed to get session-on-behalf-of authorization requirements

4146
Internal Error: Failed to get the session-on-behalf-of header

4147
AuthorizeSessionOnBehalfOf for delegate failed

4148
Internal Error: Failed to read from the authorized delegate reader

4149
Delegator is not found in the deployment

4150
P-Session-On-Behalf-Of header has params which are disallowed

4151
HTTP Authorization for P-Session-On-Behalf-Of header failed

4152
Remote authorization of delegate failed

4153
Remote authorization of delegate timedout

4154
Endpoint is not currently registered and a re-registration required for this operation.

4155
Internal Error: Failed to set tenant context ID

4156
Internal Error: Failed to set tenant boundary ID

4157
Internal Error: Failed to get tenant context ID

4158
Delegate Request: session-on-behalf-of header absent

4159
Delegate Request: SIP To is not equal to the session-on-behalf-of header

4160
Internal Error: Failed to deserialize the context containing user pool information

4161
Target Endpoint is not registered

4162
Internal Error: Failed to determine the service that needs to handle the request

4163
Internal Error: PoolManager failed to process request.

4164
Presence service is unavailable. This client does not support registration in the absence of the presence service and hence registration is being denied.

4165
User Services Pool is unavailable.

4166
Preferred Registrar Change.

4167
Preferred Pool Change.

4168
Internal Error: Failed during string manipulation

4169
Internal Error: Failed to get Security Handle

4170
Internal Error: Failed to execute GetPublishedCertAndAuthorize

4171
GetPublishedCert uprp command failed

4172
No cert found for the user

4173
Internal Error: GetPublishedCert command timed out

4174
Internal Error: Failed to determine the primary and backup pools to handle the request.

4175
Internal Error: Failed to read from the published cert reader

4176
Internal Error: Failed to get the UserServices pool from Context

4177
Internal Error: Failed while invoking UPRP command GetPublishedCert

4178
Invalid or Unknown Service Pool Type

4179
User homed on W13 Pool. Cert Auth is not possible

4180
Failed to determine the primary pool to handle request. This could be a temporary issue.

4181
The health information of the primary pool is being evaluated. This could be a temporary issue.

4182
GetSubscriptionVersioning failed

4183
Failed to determine the deployment location to handle request.

4184
Internal Error: Failed to redirect request

4185
Internal Error: Failed to get the ms-split-domain-info header

4186
Internal Error: Failed to set the ms-split-domain-info header

4187
Failed to cache publications on registrar.

4188
Failed to determine the Delegator’s Pool for authorization.

4189
User object is not configured properly.

4190
Failed to determine the user’s pool to process request.
The user’s home pool is not configured properly in Active Directory. This can occur if the pool was decommissioned or if a user move failed. Administrators should use the Set-CsUser commandlet to update the user’s home pool information.

4191
Internal Error: Failed while invoking SPROC GetPublishedCert

4192
RtcUpdateEndpoint Sproc failed.

4193
UpdateEndpoint Http Request Failed.

4194
Failed to get traffic type from the ms-split-domain-info header

4195
Internal Error: Failed to delete the ms-split-domain-info header

4196
From or target user pool or deployment assignment is incompatible with split-domain traffic type

4197
MWI Notify body parse failure

4198
Not a valid Sip URI in the From or To header

4199
Multiple users associated with the target phone number

4200
SIP Identity is required for Delegate Authorization

4201
SIP Identity required for processing this request

4202
Internal Error: Failed to add P-Asserted-Identity header.

4203
The Sip URI in the From and To header are not identical

4204
The Sip URI in the From and To header contains a user portion which is not allowed

4205
From User Policy is not Found.

4206
To User Policy is not Found.

4207
External Access Policy Processing Failed.

4208
Internal Error: Failed processing contact header.

4209
Internal Error: Failed processing expires header.

4210
Internal Error: Failed to get the content of a header.

4211
Internal Error: Failed to read from the endpoint reader.

4212
Internal Error: Failed to send response.

4213
Internal Error: Request is incorrectly targeted at the ICR

4214
Tenant Federation Configuration Processing Failed.

4215
MWI Notify for legacy user cannot be processed.

4216
An internal error occurred while User Services was processing the request.

4217
Internal Error: Failed to get user portion from URI

4218
Internal Error: Failed to get FQDN from URL

4219
Authentication took too long

4220
Failed to get remote FQDN from the ms-split-domain-info header

4221
Failed to get home route from the ms-split-domain-info header

4222
Cannot redirect user to the deployment location pointed to by SRV record

4223
Deployment location loop detected: request arrived from the deployment location of the target user

4224
Cannot route request to the home pool of the From user because From user is not homed in this deployment

4225
Cannot route request from home deployment of target user without pre-populated destination route

4226
Cert auth is not allowed for users homed on remote deployments

4227
Dialog Routeset Update Required

4228
User Services Pool is unavailable as backend database failover is in progress.

4229
This user is either failing over or failing back to another server and User Store has been locked for the transition

4230
Pool has been failed over to its backup

4231
Internal error while trying to route via ICR

4232
Pool Manager indicates that there are no servers available to process this request

4233
Presence and Conferencing services are not available because the User Store is down or the connectivity to datacenter has been lost

4234
Internal error while trying to find backup server

4235
Internal error while trying to send the request to director in correct forest

4236
Internal error while trying get the director for remote forest

4237
Internal error while trying to get ms-routing-phase header

4238
Internal error while trying to delete ms-routing-phase header

4239
Internal error while trying to set ms-routing-phase header

4240
Server has detected a loop

4241
Subscription is being terminated because contact has been moved to another pool.

4242
Internal error during Lookup User operation.

4243
Lookup User failed to find a server to perform authorization.

4244
User Group is not registered with Pool Manager.

4245
Pool state is being reconfigured. This is a transient condition.

4246
Failed to proxy request to owning FE.

4247
Request was proxied to owning FE but it timed-out

4248
Failed to Execute Query Resource Data Sproc

4249
Resource is in a remote deployment, but no destination available.

4250
Cannot route request from a deployment that is not a home deployment of the destination user.

4251
Transport error while executing a replication command.

4252
Backup Store is unavailable.

4253
Internal error while executing a replication command.

4254
Time-out without final response.

4255
Request cannot have a non-empty body.

4256
Internal Error: Failed to get FROM uri string

4257
Internal Error: Failed to determine if from URI is phone

4258
A Quorum of Servers is not available to commit this operation.

4259
Contact list is rolled back from exchange.

4260
Primary pool is being failed over to its backup and hence User Store is locked for the transition

4261
Pool is now failing back and hence User Store is locked for the transition

4262
User is homed on this Server, but is currently in read-only mode (1). This is a transient condition during Failover/Failback

4263
User is homed on this Server but is currently in read-only mode due to lack of write quorum. This is be a transient condition during Failover/Failback

4264
User is homed on this Server but is currently in read-only mode due to pending reconfiguration. This is a transient condition during Failover/Failback

4265
User is homed on this Server but is currently in read-only mode. Because FE was demoted, but it hasn’t gotten a notification with the address of the new primary. This is a transient condition during Failover/Failback

4266
User is homed on this Server but is currently in read-only mode (2). This is be a transient condition during Failover/Failback

4267
User is homed on this Server but is in read-only mode as Backup Store is unavailable. This is be a transient condition during Failover/Failback

4268
Delegate operation not allowed as delegate and delegator are in different deployments.

4269
The request is targeted to registrar-only server or pool, which cannot serve user services requests

4270
Failed to parse ms-subnet header

5000
One or more critical applications are not running

5001
A request was sent to the callee’s pool but no further response was received.
This failure can occur if the callee’s pool is busy. Administrators should check the callee’s pool for load or capacity issues. Administrators should also check the topology for any network related errors.

5002
Request was cancelled

5003
Internal processing failure

5004
Failed parsing the incoming request

5005
The application specified an invalid request-uri

5006
Failed when constructing the outgoing request

5007
Failed processing a contact entry

5008
The application specified an invalid static forwarding url

5009
Bye/Ack is being sent on receipt of 200 as the Invite transaction has been canceled

5010
Application is canceling a client transaction for which we have received a 2XX, sending Bye/Ack instead

5011
ACK is being generated on receipt of a 487 canceled response for an INVITE forked by application

5012
ACK is being generated on receipt of a failure final response for an INVITE forked by application

5013
ACK is being generated as the Invite transaction timed-out

5014
BYE/ACK for client transaction on receipt of a 2XX response on another client transaction.

5015
BYE/ACK for client transaction on receipt of a 6XX response on another client transaction.

5016
Request handler threw an exception

5017
ACK is being generated on receipt of a failure final response for an INVITE forked by application

5018
Client initiated Cancel

5019
Cancel sent as original INVITE timed-out

5020
Cancel sent as original INVITE received 2XX response from another fork

5021
Cancel sent as original INVITE received 6XX response from another fork

5022
Cancel sent as original INVITE received final non-2XX/non-6XX response from another fork

5023
Cancel sent as INVITE client transaction timed-out

5024
Cancel sent as INVITE client transaction was in ringing state for too long.

5025
Cancel sent by application for INVITE client transaction.

5026
The request was sent to the callee’s client endpoints but no further response was received.
This can happen if the callee’s endpoint disconnected in the middle of the operation (e.g., the laptop was closed). This can also occur if the callee’s endpoint is busy, crashed, or disconnected abnormally.

5027
Response handler threw an exception

6000
SIP request send failed
Error as a result of failing to send a message thru sip stack

6001
Request Timeout
Error as a result of sip transaction timing out

6002
Dialog/Transaction does not exist
Error as a result of request arriving in a dialog that does not exist

6003
Unsupported out of dialog request
Error as a result of unsupported request arriving out of dialog

6004
Media type is not supported
Error as a result of media type in request not supported

6005
Invite session is not setup
Error as a result of request arriving before invitesession is setup

6006
Mcu is shutting down
Error as a result of request arriving when mcu is shutting down

6007
Conference uri not present in request
Error as a result of conference uri not present in the incoming Invite

6008
Conference represented by conf uri does not exist
Error as a result of conference not being found

6009
Message has exceeded maximum allowed length
Error as a result of message having exceeded maximum allowed length

6010
Authorization failure
Error as a result of authorization failing for the INVITE request

6011
User not found
Error as a result of user specified by request not being found

6012
Participant is not expected to be incoming
Error as a result of dialin for a participant that is not marked incoming

6013
Conference is terminated
Error as a result of request arriving after conference is terminated

6014
Unexpected (re)invite request
Error as a result of an unexpected invite or re-invite request

6015
SDP is not acceptable
Error as a result of request arriving with unsupported sdp

6016
Unsupported request type
Error as a result of request type not supported

6017
Info body has exceeded maximum allowed length
Error as a result of info body too large

6018
Invite session is disconnected
Error as a result of request arriving in a disconnected invite session

6019
Dialog does not exist
Error as a result of request arriving after dialog has been terminated

6020
Failed to process session timer
Error as a result of failure in processing session timer

6021
Ack was not received from the client
Error as a result of not receiving Ack from the client to complete Invite dialog

6022
Invite dialog was terminated
Error as a result of the Invite dialog being terminated before the session to client is connected

6023
User was deleted
Error as a result of the User being deleted

6024
Message does not contain a format acceptable to the client
Error as a result of the failure to forward the message to a client as the message does not contain a format that is acceptable to the client

6025
Require header has an unsupported SIP extension
The Invite request contains a Require header with an unsupported SIP extension

6026
Bye sent due to the conference being deleted
The Bye request was sent because the conference associated with the call leg was deleted

6027
Bye sent due to Error response to a request on the Invite dialog
The Bye request was sent due to an error response to a request sent on the Invite dialog

6028
Bye sent as there was no update before the session timer expired
The Bye request was sent as no update request was received before the session timer expired.

6029
Bye sent due to error in processing Invite response
The Bye request was sent as there was an error in processing the success response to the Invite request

6030
Invite request does not have gruu/sipinstance/epid
The INVITE request has no gruu or sipinstance or epid

6031
IM MCU is muted and therefore not accepting IM messages
The MESSAGE request was declined because IM MCU is muted

7000
Maximum number of meetings exceeded – server is too busy
Maximum number of meetings exceeded – server is too busy

7001
NAT/Firewall traversal service not available
The Audio-Video Conferencing Service could not contact the A/V Access Edge for credentials. This prevents external users from joining, can potentially result in connectivity issues for internal users, and in Edgeless BW managed deployments results in BW controls not being honored. The failure can be caused by mis-configuration of the A/V Access Edge (or PDP Access Edge) or due to infrastructure/routing issues  For resolution, please check if the Audio-Video Conferencing Service KHI has been logged for Infrastructure failures and correct the issue. Otherwise please check the Audio-Video Access Edge for configuration issues.

7002
The specified conference does not exist
The user is trying to join a conference that does not exist on the Audio-Video Conferencing Service.This failure can occur if an endpoint is trying to join a conference that does not exist anymore. This may occur due to a race condition or due to the Focus conference and the Audio-Video conference instances being out of sync due to excessive load on the Conferencing Servers and/or Network Congestion. For resolution, please address load or congestion issues. If this error continues to happen  consistently please contact Microsoft for additional assistance in fixing the issue.

7003
The SIP INVITE request with the client timed out
The Audio-Video Conferencing Service SIP INVITE request to the endpoint timed out without a response. This failure can occur due to connectivity issues with an endpoint, or due to a crash, or a hang or network connectivity failing. If this issue occurs between OCS server components, it should be resolved by correcting network connectivity issues. However, it is possible for client endpoints to experience hangs/crashes.

7004
The AV MCU supports only ‘Content-Type: application/sdp’ offer/answers
The Audio-Video Conferencing Service supports only Session Description Protocol (SDP) offers and answers for Media Session Negotiation The client is trying to use an unsupported protocol with the Audio-Video Conferencing Service. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7005
The request is malformed or unexpected at this time
The Audio-Video Conferencing Service received a malformed  SIP or C3P request which it was unable to process. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7006
Conference not provisioned for this user
This user was not provisioned for the conference with an Adduser request. This failure might occur due to behavior within the OCS 2007, OCS 2007 R2 clients (including LiveMeeting)

7007
Replacing existing user is not allowed
Additional C3P adduser requests were received for a user for whom a C3P adduser request is already being processed for Audio-Video Conference Join. This may also occur if the original C3P adduser request does not allow replacing the original session.If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7008
Error parsing SDP
The Audio-Video Conferencing Service encountered an error while parsing SDP. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7009
IPv6 connection address not supported
The Audio-Video Conferencing Service does not support IPv6 IP addresses. Please configure OCS components involved in Audio-Video Conferencing with IPv4 addresses.

7010
Error parsing SDP: Missing or invalid connection address
The Audio-Video Conferencing Service received missing or invalid connection addresses. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issues. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7011
Error parsing SDP: Unrecognized or incompatible media transport profile
The Audio-Video Conferencing Service received an invalid/unsupported media transport profile. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7012
Cannot support media encryption required by client
The Audio-Video Conferencing Service received a media encryption format that it cannot support. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issues. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7013
SRTP-encrypted media required to join
The Audio-Video Conferencing Service cannot process this session because SRTP encrypted media is required to join and not available from the endpoint trying to join. Please provision the endpoint trying to join to offer SRTP encrypted media to the Audio-Video Conferencing Service, or configure the Audio-Video Conferencing service to allow non-encrypted sessions.

7014
Error parsing SDP: Invalid ICE transport candidates
The Audio-Video Conferencing Service encountered an error parsing SDP because the endpoint offered INVALID transport candidates for Media Connectivity. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7015
Cannot change SRTP encryption key
The Audio-Video Conferencing Service does not support changing the encryption key for media streams after initial offer answer. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7016
Call cannot start on hold
The Audio-Video Conferencing session cannot start as being on HOLD. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7017
Cannot modify media while call on hold
It is not possible to modify their media route, while on HOLD. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7018
Error parsing SDP: invalid RTP or RTCP port value
The Audio-Video Conferencing Service received an invalid RTP/RTCP port value in the SDP Offer/Answer and cannot process the media session If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7019
Error parsing SDP: invalid number of media
The Audio-Video Conferencing Service endpoint received an invalid number of media in the SDP during media negotiation and terminated the session. This failure might occur due to behavior within the OCS 2007, OCS 2007 R2 clients, but should not occur with Lync Server 2010. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft Lync 2010 endpoints please contact Microsoft for additional assistance in fixing the issue.

7020
Error parsing SDP: mismatched or out-of-order media
The Audio-Video Conferencing Service endpoint received out of order or mismatched media in the SDP during the media negotiation phase. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7021
Error parsing SDP: client must provide only one SRTP encryption key
The Audio-Video Conferencing Service received multiple SRTP encryption keys in the SDP during the media negotiation phase. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7022
Cannot support any media offered by client
The Audio-Video Conferencing Service received an invalid media type in the SDP during the media negotiation phase. This might be due to endpoint returning an unsupported media type (non-AV), or due to a mismatch between the media offered by client, and what is allowed by the Conference policy. May happen if only video is offered for audio only conference – AllowIPVideo is disabled, or only audio is offered for a conference where only video is enabled allow IPAudio is disabled.) This issue should not take place in a well configured deployed, where Meeting Policy for users is properly configured. Please check meeting policy for consistency (in AllowIPAudio, AllowIPVideo  If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7023
Client declined all media
The endpoint trying to join the Audio-Video Conferencing Session declined all media in SDP during media negotiation. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7024
Failure negotiating SRTP encryption for media
The Audio-Video Conferencing Service failed to negotiate media encryption with the endpoint. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7025
Internal server error creating media for user
The Audio-Video Conferencing Service encountered an internal error during media negotiation for a user. The issue can occur due to premature changing of media negotiation parameters in SDP before media negotiation is complete. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7026
Failed to establish media connection with client
Media Connectivity establishment for the Audio-Video Conferencing session failed. This issue can occur a network path for media to flow is not available. This may happen due to firewalls being present inside the enterprise network, or if the Audio-Video Conferencing service or the Endpoint joining the conference cannot reach the Audio-Video Access Edge for participants outside of the enterprise network. A common cause for this is that a legacy client needs to be patched (KB 2028888). This will only be reported by OCS 2007, OCS 2007 R2 AV Conferencing server.

7027
The media connection with the client was lost
The Audio Video Conferencing session ended due to the media session timing out.  This may occur if the endpoint ends the Audio-Video Conferencing session without properly terminating the SIP session, due to the endpoint crashing, or losing network connectivity.

7028
Requested custom route not allowed by policy
The custom media routing request sent by the user cannot be allowed in this Audio-Video Conference. Under certain conference modes or user roles, the user may not be allowed to modify the media routes for themselves/or 3rd party contained in the request.  If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7029
Server is busy
The Audio-Video Conferencing server is overloaded and is experiencing degraded global health, due to which it cannot accept new sessions or conferences. This issue is caused when the Audio-Video Conferencing Service is overloaded and does not have sufficient Hardware resources to support more users. If this issue occurs consistently, add more machines to support audio-video conferencing usage in the deployment.

7030
User is replaced
The user joined the Audio-Video Conferencing Session from another endpoint and the original endpoint was replaced.

7031
Audio-Video Conferencing Service is shutting down
The session is being ended due to the Audio-Video Conferencing service being shut down. The cause can be an admin initiated shutdown, or an unplanned outage. Please check the status of the Audio-Video Conferencing Service and make sure the service is running properly to resolve the issue.

7032
Encountered errors sending SIP message
The Audio-Video Conferencing Service encountered an internal error while trying to send a SIP message. If this issue occurs frequently, please contact Microsoft for additional assistance in fixing the issue.

7033
The client is attempting to join another endpoint that has not been provisioned
The client is trying to join the Audio-Video Conference  from a second endpoint which is not provisioned with a C3P adduser request. If this issue occurs frequently, please contact Microsoft for additional assistance in fixing the issue.

7034
User removed from conference
The user was removed from the Audio-Video conferencing session.

7035
User removed due to conference ending
The user was removed from the conference upon the Audio-Video conference ending.

7036
Media Connectivity Issues in call
Non- fatal Media Connectivity issues were experiences during the call with Audio or Video. This diagnostic is caused when an additional modality (video, pano-video) is declined due to bandwidth constraints in a Bandwidth managed deployment, or if there are non-fatal issues with adding modalities (video, pano) during an Audio-Video Conferencing session.

7037
Media stack diagnostics info
This diagnostics code contains internal debug information for Media Connectivity establishment.

7038
Conference is being shut down
The user was added to a conference that was shut down.

7039
Sip transaction is currently pending
Sip transaction is currently pending

7040
Received unrecoverable failure response for Sip transaction
Received unrecoverable failure response for Sip transaction

7041
All media instances have been declined by client and server
All media instances have been declined by client and server

7042
Server internal error in AVMCU
Server internal error in AVMCU

7043
Terminating app invite dialog
Terminating app invite dialog

7044
Requested AddUser not allowed by policy
The AddUser request sent by the user cannot be allowed in this Audio-Video Conference. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for flaws/interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue.

7045
Terminating SIP response from remote endpoint did not contain diagnostic information
Terminating SIP response from remote endpoint did not insert ms-diagnostics or ms-client-diagnostics headers

7046
AVMCU Join Time Information
This diagnostics code contains internal debug information for measuring join time.

7047
Requested source not available
This diagnostics code contains description of Modify Conference failure

8000
Failed to establish session with ACP partner.
Unexpected Error

8001
Failed to bootstrap acpmcu to connect with ACP partner.
Unexpected Error

8100
Failed to establish focus session.
Unexpected Error

8101
Did not find avmcu conference uri.
Unexpected Error

8102
GetConference request for given conference failed.
Unexpected Error

8103
Failed to send add user request for bridging.
Unexpected Error

8104
Conference bridge terminated unexpectedly.
Unexpected Error

9000
Request is malformed
Request contains an error. Check if it conforms to the schema.

9001
Request is too large
The number of credentialsRequest in the request exceeds the number specified in the schema.

9002
Internal server error
The server has encountered an unexpected error.

9003
Not supported

9004
Server busy

9005
Timeout

9006
Request is forbidden
Client might be sending more than one credentialsRequest or is requesting tokens for somebody else.

9007
Ok

9008
Version not supported
Server does not support the version provided by the client.

9009
Other failure

9010
Unsupported message type
Only SERVICE requests are allowed.

9011
Unsupported content type
Content type is unsupported.

9012
Draining
Server is in draining mode.

9013
Not a trusted server
This type of request should be sent only by a trusted server. The sender was not identified as a trusted server.

10000
Gateway returned a SIP failure code
The failure is due to an error code returned by the gateway.

10001
Gateway did not respond in a timely manner (timeout)
The gateway did not send a SIP response within the accepted timeframe.

10002
Gateway did not return a response
The gateway sent back an incomplete SIP response message.

10003
Proxy returned a SIP failure code
The failure is due to an error code returned by the proxy.

10004
Proxy did not respond in a timely manner (timeout)
A response to a SIP message sent to the Proxy side was not received within the allotted time.  This could occur if a client is slow to respond, or some issue in the Proxy side makes it unable to respond in a timely manner.

10005
Proxy did not return a response
The proxy sent back an incomplete SIP response message.

10006
Proxy side Media negotiation failed
Failure when processing the SDP from the proxy. ie. parsing failures, incompatible codecs, lack of SDP, etc.

10007
Proxy side media stream timeout
Proxy side receive RTP stream timed out.

10008
Incoming request has invalid parameters
Cannot create the outgoing session based on the incoming session parameters. Incoming Request has invalid parameters.

10009
Mediation Server is shutting down
The incoming call cannot be serviced because Mediation Server is shutting down.

10010
Gateway side Media negotiation failed
Failure when processing the SDP from the gateway. ie. parsing failures, incompatible codecs, lack of SDP, etc.

10011
Media Gateway side stream timeout
Gateway side receive RTP stream timed out.

10012
Call rejected because Mediation Server is in draining mode
The incoming call cannot be serviced because Mediation Server is draining.

10013
Gateway peer in inbound call is not found in topology document or does not depend on this Mediation Server
This gateway cannot be mapped to a PSTNGateway object in the topology document or does not have a dependency on this Mediation Server.

10014
An internal exception received while processing the incoming request
The incoming request was rejected because Mediation Server encountered an internal error.  Please check the traces to get more information regarding the scenario.

10015
Processing another INVITE with replaces request
The incoming INVITE with replaces call cannot be serviced because the existing call is already processing another INVITE with replaces request.

10016
Mediation Server global health threshold has been exceeded
The incoming call cannot be serviced because Mediation Server is resource limited.

10017
Mediation Server does not support INVITE with Join
The incoming call was rejected because Mediation Server does not support INVITE with Join.

10018
The MIME in offer is invalid
The MIME in offer is invalid.

10019
No application/sdp content found in the incoming MIME body
The incoming call was rejected because the included MIME body did not contain an application/sdp part.

10020
Cannot process INVITE with replace because call leg is not in valid state
The incoming INVITE with replaces call cannot be serviced because the existing call is not in a valid state.

10021
Cannot find call leg to replace
The referenced call in the incoming INVITE with replaces does not correspond to a known call on this Mediation Server.

10022
Exception with received INVITE with replaces.
Exception with received INVITE with replaces.

10023
From header is incorrectly formatted
The From header in the incoming INVITE is incorrectly formatted.

10024
To header is incorrectly formatted
The To header in the incoming INVITE is incorrectly formatted.

10025
Gateway peer in outbound call is not found in topology document or its internal settings are not configured properly.
This destination gateway cannot be mapped to a PSTNGateway object in the topology document or its internal settings are not configured properly.

10026
This call leg has been replaced
This call leg has been replaced by an INVITE with replaces

10027
Normal termination response from gateway after the call was established
An active call was terminated in a normal fashion. ie. due to the remote party hanging up

10028
Unexpected call termination from gateway side
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10029
Call leg has been redirected
This call leg has been redirected.

10030
Terminating call leg because the end to end call was shut down
This call leg, associated with a REFER or INVITE with replaces request, was terminated because the end to end call was shut down.

10031
Call rejected because the Mediation Server service is paused
The incoming call cannot be serviced because Mediation Server is paused.

10032
Media diagnostic information
This diagnostics header includes raw media diagnostic data.

10033
Cannot process reINVITE because call leg is not in valid state
The incoming reINVITE call cannot be serviced because the existing call is not in a valid state.

10034
Proxy SIP dialog recovery has failed
An attempt to recover the signaling session for this call has timed out.

10035
TLS negotiation failed with the Mediation Server next hop peer.
Mediation Server encounted a TLS negotiation failure with its next hop peer.

10036
Cannot process refer because call leg is not in valid state
The incoming REFER call cannot be serviced because the existing call is not in a valid state.

10037
Normal termination response from gateway before the call was established
The call was terminated because the gateway sent a CANCEL before the call was established.

10038
No application/sdp or applicable application/gw-sdp content found in the incoming INVITE
The call cannot be established because no applicable application/sdp or application/gw-sdp content has been found in the incoming INVITE request.

10039
Outbound call is directed to Mediation Server but is not replacing an existing call
This call to Mediation Server cannot be handled without a Replaces header.

10040
Unexpected call termination from gateway side, ITU-T Q.850 Cause resource unavailable class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10041
Unexpected call termination from gateway side, ITU-T Q.850 Cause service or option unavailable class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10042
Unexpected call termination from gateway side, ITU-T Q.850 Cause service or option not implemented class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10043
Unexpected call termination from gateway side, ITU-T Q.850 Cause invalid message (e.g. parameter out of range) class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10044
Unexpected call termination from gateway side, ITU-T Q.850 Cause protocol error (e.g. unknown message) class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10045
Unexpected call termination from gateway side, ITU-T Q.850 Cause interworking class
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10046
Unexpected call termination from gateway side, outside ITU-T Q.850 Cause definition
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10047
Unexpected call termination from gateway side, request has an unexpected reason header or cause code format
An active call was terminated in an abnormal fashion. ie. due to a reason other than the remote party hanging up

10048
The operation to repatch the original call after a 3pcc refer failure has failed.
The operation to repatch the original call after a 3pcc refer failure has failed.  The original call cannot be recovered so Mediation Server is terminating the call.

10049
The current signaling session took too long to establish the connection, so the call leg was canceled.
The current signaling session took too long to establish the connection, so the call leg was canceled.  This can happen because a recipient did not answer the call.

10050
Mediation Server only supports 200 OK response with SendRecv stream direction in the initial call setup
An inbound call received a 200 OK response with a stream direction other than SendRecv.  Mediation Server only supports 200 OK response with SendRecv stream direction in initial call setup.  The UC side component is not compatible with Mediation Server.

10051
The socket connection attempt to this gateway took too long, so the call leg was canceled.
The socket connection attempt to this gateway took too long, so the call leg was canceled.  This means Mediation Server was not able to reach the designated trunking peer.

10052
Terminating call as it is answered earlier than the specified voicemail escape timer
This call was terminated because it is answered earlier than the specified voicemail escape timer.

10053
Expected call termination from gateway side, Cause 102 Recovery on timer expiry of the ITU-T Q.850 Cause protocol error (e.g. unknown message) class
An active call was terminated in a normal fashion. ie. due to no answer from the remote party

10400
Gateway responded with 400 Bad Request
This response from a gateway can occur if the gateway does not understand a SIP request due to malformed syntax or an invalid destination number.

10401
Gateway responded with 401 Unauthorized
This response from a gateway can occur if user authentication is required.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Check that the gateway does not require authentication on the sip connection to Mediation Server.  Please refer to gateway documentation for more details.

10402
Gateway responded with 402 Payment Required
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10403
Gateway responded with 403 Forbidden
This response from a gateway can occur if the gateway understood the request, but is refusing to fulfill it.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Check that the dial plan configured in the Gateway/Trunk allows to establish the desired call.  Please refer to gateway documentation for more details.

10404
Gateway responded with 404 Not Found (User Not Found)
This response from a gateway can occur if the gateway has information that the user cannot be reached or does not exist in the remote network.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10405
Gateway responded with 405 Method Not Allowed
This response from a gateway can occur if the gateway is not configured to accept SIP INVITE requests.  Please refer to gateway documentation for more details.

10406
Gateway responded with 406 Client Not Acceptable
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10407
Gateway responded with 407 Proxy Authentication Required
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Check that the gateway does not require authentication on the sip connection to Mediation Server.  Please refer to gateway documentation for more details.

10408
Gateway responded with 408 Request Timeout
This response from a gateway can occur if no user on the PSTN responded within a suitable amount of time, or a network equipment is blocking SIP messages from Mediation Server to the gateway.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  If this is a persistent problem, verify SIP messages in the call establishment stage are routed correctly between the Mediation Server and the gateway.  Please refer to gateway documentation for more details.

10409
Gateway responded with 409 Conflict
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10410
Gateway responded with 410 Gone
This response from a gateway can occur if a PSTN phone number has been changed or does not exist anymore.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10412
Gateway responded with 412 Conditional Request Failed
Please refer to gateway documentation for more details.

10413
Gateway responded with 413 Request Entity Too Large
This response from a gateway can occur if the body of the request is larger than the gateway can process.

10414
Gateway responded with 414 Request URI Too Long
This response from a gateway can occur if the Request-URI is longer than the gateway is willing to interpret.

10415
Gateway responded with 415 Unsupported Media Type
Ths response from a gateway can occur if the gateway is not configured to accept the message body of the request.

10416
Gateway responded with 416 Unsupported URI Scheme
This response from a gateway can occur if the scheme of the Request URI is unsupported by the gateway.  Check that the gateway supports E.164 numbers as described in RFC 3824.

10417
Gateway responded with 417 Unknown Resource Priority
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10420
Gateway responded with 420 Bad Extension
This response from a gateway can occur if the gateway did not understand the protocol extension specified in a Require header field.

10421
Gateway responded with 421 Extension Required
This response from a gateway can occur if the gateway needs a particular extension to process the request, but this extension is not listed in a Supported header field from Mediation Server.

10422
Gateway responded with 422 Session Interval Too Small
This response from the gateway can occur if the session timer configuration is not correct for interop with Mediation Server.  Please refer to gateway documentation for more details.

10423
Gateway responded with 423 Interval Too Brief
Please refer to gateway documentation for more details.

10424
Gateway responded with 424 Bad Location Information
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10428
Gateway responded with 428 Use Identity Header
Please refer to gateway documentation for more details.

10429
Gateway responded with 429 Provide Referrer Identity
Please refer to gateway documentation for more details.

10433
Gateway responded with 433 Anonymity Disallowed
Please refer to gateway documentation for more details.

10436
Gateway responded with 436 Bad Identity Info
Please refer to gateway documentation for more details.

10437
Gateway responded with 437 Unsupported Certificate
Please refer to gateway documentation for more details.

10438
Gateway responded with 438 Invalid Identity Header
Please refer to gateway documentation for more details.

10480
Gateway responded with 480 Temporarily Unavailable
This response from a gateway can occur if the callee’s end system was contacted successfully over the PSTN, but the callee is currently unavailable.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10481
Gateway responded with 481 Call Transaction Does Not Exist
This is a temporary condition where a sip request was received by the gateway after it has sent a clearing message.  Please refer to gateway documentation for more details.

10482
Gateway responded with 482 Loop Detected
Please refer to gateway documentation for more details.

10483
Gateway responded with 483 Too Many Hops
Please refer to gateway documentation for more details.

10484
Gateway responded with 484 Address Incomplete
This response from a gateway can occur if the destination number is invalid.  Please refer to gateway documentation for more details.

10485
Gateway responded with 485 Ambiguous
Please refer to gateway documentation for more details.

10486
Gateway responded with 486 Busy Here
This response from a gateway can occur if the destination user is busy.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10487
Gateway responded with 487 Request Terminated
This response from a gateway happens if the call was cancelled from the originator.

10488
Gateway responded with 488 Not Acceptable Here
This response from a gateway can occur if there is a configuration discrepancy between Mediation Server and the gateway that affects call parameter negotiation.  Please refer to gateway documentation for more details.

10489
Gateway responded with 489 Bad Event
Please refer to gateway documentation for more details.

10491
Gateway responded with 491 Request Pending
This response from a gateway can occur if the gateway cannot accept this request because of a pending operation.  Please refer to gateway documentation for more details.

10493
Gateway responded with 493 Undecipherable
Please refer to gateway documentation for more details.

10494
Gateway responded with 494 Security Agreement Required
Please refer to gateway documentation for more details.

10495
Gateway responded with 409 Conflict with ITU-T Q.850 Cause code 98 Message Not Compatible
Please refer to gateway documentation for more details.

10500
Gateway responded with 500 Server Internal Error
This response from a gateway can occur if the gateway encountered an unexpected condition that prevented the request from being fulfilled. If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10501
Gateway responded with 501 Not Implemented
Please refer to gateway documentation for more details.

10502
Gateway responded with 502 Bad Gateway
This response from a gateway can occur if the gateway received a bad response from its next hop PSTN entity (PBX, network switch). If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10503
Gateway responded with 503 Service Unavailable
This response from a gateway can occur if the gateway or intermediate PSTN entity is not in a state that can process the request. For example, if all trunks to the PSTN are busy, or the gateway has been placed in a maintenance condition.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated. Please refer to gateway documentation for more details.

10504
Gateway responded with 504 Server Time out
This response from a gateway can occur if the gateway did not receive a timely response from its next hop PSTN entity.

10505
Gateway responded with 505 Version Not Supported
Please refer to gateway documentation for more details.

10513
Gateway responded with 513 Message Too Large
Please refer to gateway documentation for more details.

10580
Gateway responded with 580 Precondition Failure
Please refer to gateway documentation for more details.

10600
Gateway responded with 600 Busy Everywhere
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10603
Gateway responded with 603 Decline
This response from a gateway can occur if the destination user or system has declined to accept the call.  If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10604
Gateway responded with 604 Does Not Exist Anywhere
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

10606
Gateway responded with 606 Server Not Acceptable
If the sip-reason parameter is available, this will contain the specific ISDN/ISUP Cause code from the PSTN interaction with the gateway that triggered this response to be generated.  Please refer to gateway documentation for more details.

11000
URI validation failed

11001
The report type or version is not supported

11002
The metrics report contains one or more invalid values

11003
The metrics report was rejected due to schema validation failure

11004
Only the SIP SERVICE method is supported

11005
The content type is not supported

11006
The report body exceeded the maximum allowed size

11007
QoE is not enabled

11008
Server over loaded

11009
Data collection internal processing failure

12000
Routes available for this request but no available gateway at this point
The user’s call could not be routed because all available PSTN gateways have been marked as down.  Administrators should check the caller’s voice policy to see where the dialed number would be routed, and verify that specified gateways are all functioning properly. Diagnostics sent in provisional responses may contain more information on the failures received from the gateways.

12001
User Policy does not contain phone route usage

12002
Phone number not valid or too large

12003
Inconsistent internal state

12004
The user is not authorized to call the specified number or none of the routes have a valid gateway configured.
Administrators should check the user’s voice policy and add a route with a usage that matches the dialed number.

12005
Error parsing policy for this user

12006
Trying next hop

12007
Could not parse flags in ms-application-via header for outbound call routing

12008
PSTN Toll Bypass disallowed

12009
PSTN Toll Bypass disallowed for Referer

12010
From URI does not match caller URI

12011
Request body does not conform to schema

12012
Number of callee URIs exceeded max limit

12013
Conference dialouts from Anonymous users disallowed

12014
The Service ID does not exist or is misconfigured

12015
The target type for vacant number entry is unknown.

12016
The redirect request from Call park service is invalid.

12017
Error occured while routing to analog device.

12018
Analog device configured on an unknown gateway

12019
Unexpected error occured while proxying request to home pool of Referred-by

12020
Unexpected error occured while processing request for non-uc enabled caller

12021
Unexpected error occured while processing request

12022
Unexpected error occured while routing request, invalid or missing ms-icr-orig-req-uri

12023
Unexpected error occured while routing request based on deployment locator of Referred-by

12024
Unexpected error occured, Hybrid voice service request received for invalid user

12025
Voice policy disallows call forwarding or simul ring to external numbers

12026
ACP Gateway to be used is unknown

12027
Call to ACP Gateway failed

12028
The call is not allowed due to Location based routing restrictions

12029
The user is not authorized to call the specified number from this location or none of the routes have a valid gateway configured.

13000
Call to self loop
This can occur if a user configures a call forwarding rule to their own enterprise number.

13001
The routing rules did not result in a suitable final response
This typically occurs when a user has configured call forwarding rules which are not permitted by policy.  For example, a user specifies that calls should be forwarded to a long distance number and the user’s policy only permits making local calls.

13002
The routing rules did not result in a final response
This is a normal behavior where the target user did not answer the call and the calling party does not permit the call to go to voicemail.  Examples include an Audio/Video Conferencing Server inviting a user to a conference or an audio call being routed to the target user’s delegates.

13003
The request contains a header that is not formatted as expected

13004
Request was proxied to one or more registered endpoints

13005
Request was proxied to one or more additional targets

13006
Request forwarded, any previous branches cancelled.

13007
Request was proxied to an application.

13008
Diagnostic headers removed for privacy.
This is a normal behavior.  This typically occurs in call forwarding scenarios to hide the receiving party’s information from the caller.

13009
No endpoints registered in Backup registrar
The target user’s primary registrar is unreachable, and the user is not registered with the backup registrar.  This could occur when a server is in resiliency mode or due to WAN connectivity issues with a branch office.

13010
Target rejected call due to bandwidth congestion

13011
Failed to dispatch request. This is an overload condition.

13012
No Routable Endpoints.
Primarily affecting Instant Messaging conversations, this error indicates that the user attempted to send a message to someone that is offline.

13013
No route exists for the requested endpoint.
This is a transient condition where Communications Server attempts to route a call to an endpoint that is no longer connected.  This typically occurs when the target endpoint lost its wireless connection or is on a laptop that entered hibernation mode.

13014
The routing rules did not result in a final response and callee is not enabled for Unified Messaging
The calling user is unable to reach or leave a voicemail for the person they are calling.  This occurs when the target user is not enabled for voicemail and does not answer the call.  It may also occur if the target user’s ‘proxyAddress’ attribute in Active Directory has not replicated to the forest where Communications Server is installed.

13015
The routing rules did not result in a final response for PSTN caller and non-UM enabled callee
The PSTN caller is unable to reach or leave a voicemail for the person they are calling.  This occurs when the target user is not enabled for voicemail and does not answer the call.  It may also occur if the target user’s ‘proxyAddress’ attribute in Active Directory has not replicated to the forest where Communications Server is installed.

13016
The routing rules did not result in a final response for App Invite
This is a normal behavior where a user is invited to an ad-hoc conference in Communicator and the user did not accept the invitation.

13017
The routing rules did not result in a final response for conference dial-out
This is a normal behavior where the target user received a dial out invitation from a conference and did not accept.

13018
The client transaction has been cancelled

13019
The client transaction has timed out

13020
An unexpected error occurred while routing request

13021
Trusted App routing invoked for an app that is not co-located

13022
The request from PSTN gateway could not be routed as it is restricted based on location

13023
The request was routed to one or more registered endpoints.

13024
The routing rules did not result in a final response. One or more endpoints were skipped due to location restriction

14000
Unknown error occurred in translation app

14001
Phone number is too long

14002
Called number not found

14003
Profile name not found in request URI

14004
An unexpected exception occurred

14005
Could not find profile in internal lookup
The dialplan requested does not exist.  This may occur in play voicemail on phone scenarios where Communications Server does not have a dialplan name that matches the Exchange Unified Messaging dialplan name.  Administrators should verify that the dialplan name specified has been defined as both a ‘location profile’ for legacy Office Communications servers and a ‘dialplan’ for new Communications Servers.

14006
Unable to find a potentially matching regex
Unable to find matching normalization rule in the dialplan

14007
Regex replace failure
Error occured while attempting to normalize the phone number using the translation regular expression

14008
Not a phone number
The URI provided is an invalid phone number.  For example, the URI may contain non-numeric characters.

14009
Tx phone num too long
The phone number obtained as a result of this normalization rule was too long.

14010
Unable to find an exact match in the rules set
The dialed number did not match any normalization rule in the Communications Server dialplan.  Administrators should verify that the dialed number is valid and, if so, add an appropriate normalization rule to the dialplan.

14011
Called Number translated

14012
Dialstring phone context used no translation done

14013
A default Dial Plan has not been configured for this pool

15000
Unable to read the user properties publication for the user or contact object.
This can occur if the hosted-voicemail contact object is not configured properly or if the information has not yet been replicated to the front end.

15001
Unexpected exception sending to UM

15002
Unable to determine dial plan

15003
The specified Exchange Unified Messaging dial plan is unknown
Communications Server may not have permissions to read the Active Directory object for this dial plan.  For example, there may be cross-forest trust issues.

15004
Exchange Unified Messaging dial plan has no servers
This issue may occur when an Exchange administrator removes all Unified Messaging servers from a dial plan or disables them during a maintenance period.

15005
UM server 302 with wrong contact count

15006
UM server sent unexpected 302 response

15007
Exchange Unified Messaging server did not respond to request
The call could not be routed to voicemail because the Exchange UM server did not respond.  This may occur if the server is too busy.  Administrators should reference the ‘dialplan’ and ‘umserver’ attributes contained in the diagnostic header of the impacted call, and verify that the specified Exchange UM server is functioning properly.  If other servers are specified in the dialplan, Communications Server will typically try to failover.

15008
Routing to UM for Subscriber Access

15009
Routing to UM for Auto-Attendant

15010
Routing to UM for voice mail deposit
This is an informational message sent in provisional responses to indicate that the Communications Server is attempting to route a call to Exchange Unified Messaging to leave a voicemail.

15011
Attempting PSTN rerouting

15012
PSTN re-routing is either not enabled, or not fully configured

15013
No Hosted Voicemail Policy could be found for the user

15014
Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null

15015
ExUM Routing Application is in an unexpected state

15016
Phone number is not properly configured for the AA/SA contact object

15017
Exchange Server did not respond in time
Exchange UM Server did not respond to the request

15018
Client transaction cancelled before final response from Exchange

15019
Client transaction terminated before final response from Exchange

15020
Too many 303 redirects

15021
No contact header in 303 redirect

15022
Invalid contact header in 303 redirect

15023
Re-directing request to the destination in 303

15024
Unexpected non-audio single-part SDP request targeted to voicemail routing

15025
Unexpected non-audio multi-part SDP request targeted to voicemail routing

15026
Unexpected non-audio non-SDP request targeted to voicemail routing

15027
Unexpected dispatch failure

15028
Target User is not Um Enabled

15029
No diagnostic information found

15030
Failed to route to Exchange Server
The call was unable to be routed to Voicemail. Diagnostics sent in the provisional responses contain more information.

15031
Exchange Server returned invalid redirection response

15032
Re-directing request to the destination in 302

15033
Failed to route call from public IM network to Exchange Unified Messaging Servers
The call was unable to be routed to Exchange Unified Messaging Servers. This might happen because of mismatch in the capabilities of the public IM client and Exchange Unified Messaging Servers. Diagnostics sent in the provisional responses may contain more information.

15034
Failed to route to Exchange Unified Messaging Server
The call was unable to be routed to Exchange Unified Messaging Server. Response code contained in the diagnostic header might indicate the potential reason for failure.

15035
Failed to route rejected by Exchange server
The call was unable to be routed to Voicemail. Call was rejected with 403, possibly user misconfigured

15036
Failed to route to Exchange server request timedout
The call was unable to be routed to Voicemail. Request timedout

15037
Failed to route rejected by Exchange server
The call was unable to be routed to Voicemail. Call was rejected with 403, possibly user misconfigured

15038
Failed to route to Exchange server request timedout
The call was unable to be routed to Voicemail. Request timedout

15500
The number of incoming calls on the Unified Messaging server has exceeded the configured maximum.

15501
The Microsoft Exchange Unified Messaging service couldn’t find a UM worker process.

15502
The Unified Messaging server cannot accept any new calls because it has been disabled.

15503
The Microsoft Exchange Unified Messaging service doesn’t have the minimum free disk space required.

15504
The Unified Messaging server is not associated with UM dial plan.

15505
Couldn’t find a valid Unified Messaging server to redirect the call.

15600
A valid UM dial plan couldn’t be found.

15601
The Unified Messaging server cannot find a valid UM hunt group associated with the UM IP gateway.

15602
The Unified Messaging server is not authorized to accept calls from this SIP peer.

15603
Transient error.

15604
Transient error.

15605
Invalid SIP header.

15606
Diversion header format is incompatible with the URI type of the UM dial plan.

15607
The local-resource-path request URI parameter is invalid.

15608
Subscriber access features can’t be invoked in a diverted call.

15609
Call answering features can’t be invoked without valid diversion data.

15610
The item ID specified in the request is invalid.

15612
Invalid SIP URI.

15613
Global gateway call failed to match any UM hunt group, user or UM auto attendant.

15614
Call was gracefully disconnected.

15615
The ms-organization parameter is required for this call.

15616
The ms-organization parameter must have a single entry for this call.

15617
The ms-organization parameter has more than three entries.

15618
The ms-organization parameter contains an invalid domain name.

15619
The ms-organization parameter doesn’t map to a valid organization.

15620
The SIP uri doesn’t map to a mailbox or a mail enabled user.

15621
The specified mailbox is not enabled for Unified Messaging.

15622
The SIP request URI format is not valid. For unauthenticated subscriber access and auto attendant calls it must contain an E.164 number. For call answering or authenticated subscriber access calls it must contain a user SIP URI.

15623
No UM dial plan or auto attendant found for the E.164 number specified.

15625
TO and FROM headers aren’t valid for this call type.

15626
Internal error. Couldn’t locate a pointer to the mailbox in global database.

15627
The mail enabled user doesn’t have a valid SMTP external email address.

15628
Receiving a SIP SERVICE request from this peer is not supported.

15629
Couldn’t find a valid Unified Messaging server to redirect the call.

15630
Invalid request.

15631
The Microsoft Exchange Unified Messaging Service was unable to redirect this call.

15632
Internal error. Couldn’t locate a pointer to the organization in global database.

15633
The ms-organization parameter doesn’t match the domain in the corresponding mail enabled user’s external email address.

15634
The Unified Messaging server is not authorized to accept calls from this SIP peer.

16000
Server over loaded

16001
Invalid request

16002
Policy disallows message contents

17000
Server over loaded

17001
Invalid request

17002
Invalid client version

17003
Declined with Url

17004
Allowed with Url

18000
Pin cannot contain non-numeric characters.

18001
Pin cannot be comprised of consecutive digits.

18002
Pin cannot be comprised of the same digit.

18003
Pin does not meet length requirements.

18004
Pin matches a previously used pin.

18005
Pin matches phone number or extension.

18006
No user policy found for the user.

18007
Pin exceeds maximum length requirements.

18008
Unexpected dispatch failure

18009
Service cannot process response messages

18010
Service received invalid message

18011
Unexpected error encountered while recording validation result

18012
Unexpected error encountered while executing UnlockPin sproc

18013
Unexpected error encountered while executing GetPinInfo sproc

18014
Internal Error: Could not extract bytes from secure string

18015
Unexpected error encountered while executing SetPin sproc

18016
Unexpected error encountered while executing GetUserPolicyAndSetPinInfo sproc

18017
Unexpected error encountered while generating hash for pin

18018
Unexpected error encountered while executing ResolveUser sproc

18019
Unexpected error encountered while getting bytes from secure string

18020
No policy assignment string for the user

18021
Failed to forward request to another FE

18022
User has been temporarily locked out
User has been temporarily locked out due to repeated attempts to authenticate using incorrect pin

18023
Permanent lockout count for the user is near or at the maximum value
Permanent lockout count for the user is about to be or has already been reached

18024
User Pin is permanently locked and needs to be reset

18025
Lookup user stored procedure failed

18026
Stored procedure for publishing certificate failed

18027
Internal Error: Failed to start lookup user state machine

18028
Internal Error: Lookup user failed

18029
Lookup user did not return any detail

18030
Lookup user did not return any frontend

18031
An unexpected error occurred

18032
Stored procedure for retrieving the certificate failed

18033
User is not homed in local forest

19000
The request is malformed or unexpected at this time.

19001
TPCP Channel already exists.

19002
TPCP Conversation already exists.

19003
The specified TPCP Conversation doesn’t exist.

19004
The specified channel-id is not the correct one.

19005
The specified converstion-entity is not the correct one.

19006
ModifyConversation w/ UserAnswered didn’t arrive in time.

19007
Failed to either deliver the call-policy-verify request or remote-service rejected the SERVICE.

19008
User doesn’t have permission to make calls to all callees.

19009
Collaboration stack encountered an error.

19010
SDP-INVITE didn’t arrive in time for incoming callflow.

19011
back-to-back failed for incoming callflow.

19012
SDP-LESS INVITE to Mediation Server failed.

19013
SELF-REFER request to Mediation Server failed to deliver.

19014
SELF-REFER request to Mediation Server failed to complete.

19015
Caller cancelled the original INVITE.

19016
TPCP converstion is in ‘Terminating’ mode.

19017
Server can’t add new conversations for this user – max limit is reached.

19018
Server doesn’t allow more than one TPCP channels per SIP dialog.

20000
Chat service busy
Error as a result of the chat server being busy where it will not accept new inbound messages

20001
Could not initialize session message queue
Error as a result of the chat server not being able to initialize the session message queue and the session.

20002
Participant failed to connect and the session information is unavailable
Error as a result of the chat server not finding participant information or the participant failing to connect.

20003
Rejected session
Error as a result of the chat server rejecting inbound session

20006
Session rejected from chat server because the session is unknown
Error occured while chat server tried to access an unknown session.

20007
Chat service error
Internal chat server error

20008
User rejected from chat server due to high server load
Error as a result of the chat server rejecting the user due to high server load.

20009
Message rejected from the chat server due to high server load
Error as a result of the chat server rejecting the message due to high server load.

20010
User rejected from the chat server due to provisioning of the user
Error as a result of the chat server rejecting the user because the user could not be found in Active Directory. Verify that the user has a valid entry in Active Directory.

20011
Message rejected from the chat server due to empty or null message body
Error as a result of the chat server rejecting the message because the message has a null or empty message body.

20012
Database is not available
Error as a result of the database not being available. Check network connectivity to the database.

20013
User rejected from chat server due to low memory available
Error as a result of the chat server not accepting the incoming user because there is not enough memory available. Check to make sure that there is enough memory on the system to run Persistent Chat.

20014
User rejected from chat server due to an unexpected number of logins
Error as a result of the chat server not accepting the incoming user because there were a large amount of logins in the last second.

20015
User rejected from chat server because they are disabled by policy
Error as a result of the chat server not accepting the incoming user because the user is not enabled by policy. Policies may take around 10-15 min to take effect.

20016
User rejected from chat server because federation is not supported
Error as a result of the chat server not accepting the incoming user because the user is federated and federation is not supported.

20017
User rejected from chat server because the memory cache is out of sync and could not store the user or the database could not update or store the user or the user could not be provisioned.
Error as a result of the chat server not accepting the incoming user because the memory cache is out of sync and unable to store the user or the database could not update and store the user or the user could not be provisioned.

20018
Non INFO message was sent on the session
Error occured as a result of the chat server trying to process a non INFO message.

21000
New sharer joined conference
A new sharer has joined the conference.

21001
Policy does not permit application sharing for this conference
This diagnostic occurs when application sharing is not permitted or disabled in meeting policy for the organizer.

21002
Attendees cannot share in this conference
This diagnostic occurs when an attendee tries to do application or desktop sharing in a conference but meeting policy does not permit it.

21003
The media connection with the client timed out.
The Application Sharing Conferencing session ended due to the media session timing out. This may occur if the endpoint ends the Application Sharing Conferencing session without properly terminating the SIP session, due to the endpoint crashing, or losing network connectivity.

21004
A presenter has started sharing content
A presenter has started sharing content in the conference.

21005
This user has joined the conference from another endpoint.
The session is terminated because the same user has joined the conference from another endpoint.

21006
The RDP connection failed to establish.
The session was terminated because the RDP connection failed to get established in a timely manner.

21007
User removed due to conference ending
The user was removed from the conference upon the Application Sharing conference ending.

21008
The Application Sharing Conferencing Service is shutting down
The session is being ended due to the Application Sharing Conferencing Service being shut down. The cause can be an admin initiated shutdown, or an unplanned outage. Please check the status of the Application Sharing Conferencing Service and make sure the service is running properly to resolve the issue.

21009
Media stack diagnostics info
This diagnostics code contains internal debug information for Media Connectivity establishment.

21010
Conference not provisioned for this user
This user was not provisioned for the conference with an adduser request

21011
The non-trusted user is not allowed to join with the specified SDP.
A non-trusted user tried to join the ASMCU by offering media that only trusted users are allowed to join with.

21012
The media connection with the client was disconnected.
The Application Sharing Conferencing session ended due to a connection error on the media channel. This may occur if the endpoint ends the Application Sharing Conferencing session without properly terminating the SIP session, due to the endpoint crashing, or losing network connectivity.

21014
The SIP connection with the client was lost.
The session was terminated due to hitting dialog resiliency mode before media could be established.

21015
User removed from conference
The user was removed from the Application Sharing conferencing session.

21017
Port allocation failed.
The ASMCU failed to allocate a media endpoint due to an internal error. This may occur if the range of ports the ASMCU is configured to use is allocated and no ports from the range are available for allocation.

21018
Server internal error in ASMCU
The session could not be established due to an internal error experienced on the ASMCU. This can happen if the ASMCU internally failed to create a conference or a user endpoint, or instantiate any basic internal components needed to host a conference.

21019
The specified conference does not exist.
The user is trying to join a conference that does not exist on the Application Sharing Conferencing Service.This failure can occur if an endpoint is trying to join a conference that does not exist anymore. This may occur due to a race condition or due to the Focus conference and the Application Sharing conference instances being out of sync due to excessive load on the Conferencing Servers and/or Network Congestion. For resolution, please address load or congestion issues. If this error continues to happen  consistently please contact Microsoft for additional assistance in fixing the issue.

21020
The conference was deactivated because the idle conference timer expired.
The conference was deactivated because the idle conference timer expired.

21021
ASMCU Join Time Information
This diagnostics code contains internal debug information for measuring join time.

22000
media negotiation failed due to unsupported media type
media negotiation failed due to unsupported media type

22001
maximum number of calls reached
maximum number of calls reached

22002
incoming request is invalid
 incoming request is invalid

22003
incoming request contains an unacceptable encryption mode
 incoming request contains an encryption mode that is not acceptable

23000
Cannot archive the message

23001
Archiving or CDR Internal processing failure

24000
Error parsing SDP
The UCMA application encountered an error while parsing SDP, possibly due to syntactically incorrect SDP. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24001
Error parsing SDP: Missing or invalid connection address
The UCMA application received missing or invalid connection addresses. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issues. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24002
Error parsing SDP: Unrecognized or incompatible media transport profile
The UCMA application received an invalid/unsupported media transport profile. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24003
Error parsing SDP: incorrect number of media lines
The UMCA application received an invalid number of media (e.g. no audio channel) in the SDP during media negotiation and terminated the session. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24004
Error parsing SDP: mismatched or out-of-order media
The UCMA application received out of order or mismatched media in the SDP during the media negotiation phase. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24005
Error parsing SDP: only one SRTP encryption key is expected
The UCMA application received multiple SRTP encryption keys in the SDP during the media negotiation phase. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24006
Error parsing SDP: Invalid ICE transport candidates
The UCMA application encountered an error parsing SDP because the endpoint offered INVALID transport candidates for Media Connectivity. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24007
Error parsing SDP: IPv6 connection address not supported
The UCMA application does not support IPv6 IP addresses. Please configure your OCS environment with IPv4 addresses

24008
Error parsing SDP: Cannot support media encryption required by client
The UCMA application received a media encryption format that cannot be supported. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issues. If this error occurs with Microsoft endpoints, please contact Microsoft for additional assistance in fixing the issue

24009
Error parsing SDP: Failure negotiating SRTP encryption for media
The UCMA application failed to negotiate media encryption with the endpoint. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24010
Error parsing SDP: SRTP-encrypted media required to establish connection
The UCMA application cannot process this session because SRTP encrypted media is required to establish connection and not available/supported from the endpoint. Please provision the endpoint to support SRTP encrypted media, or configure the UCMA application to allow non-encrypted sessions

24011
Error parsing SDP: Cannot change SRTP encryption parameters
The UCMA application does not support changing the encryption key for media streams after initial offer answer. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24012
Error parsing SDP: Cannot support any media offered by client
The UCMA application did not receive any compatible media in the SDP during the media negotiation phase. This might be due to endpoint returning an unsupported media type (e.g. video only offer).  If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24013
Error parsing SDP: Client declined all media
The endpoint trying to establish connection with the UCMA application has declined all media in SDP during media negotiation. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24014
An internal media error occurred
The UCMA application encountered an internal error during media negotiation with endpoint. The issue can occur due to premature changing of media negotiation parameters in SDP before media negotiation is complete. If this issue occurs with a non-Microsoft endpoint, please check the 3rd party implementation for interoperability issue. If this error occurs with Microsoft endpoints please contact Microsoft for additional assistance in fixing the issue

24015
Failed to establish media connection with client
Media Connectivity establishment failed between the UCMA application and the remote client outside of the enterprise network. This may happen if UCMA application has trouble connect to AV Edge server or AV Edge server is not configured or operational. A common cause for this is that a legacy client needs to be patched (KB 2028888).

24016
The media connection with the remote endpoint was lost due to RTP stream timeout
The UCMA application media connection was lost with endpoint due to the media session timing out. This may occur due to the endpoint become unavailable or lose of network connectivity

24017
The media session was terminated due to a SIP/SDP renegotiation failure
The media session was terminated between the UCMA application and the endpoint. This is due to SIP/SDP renegotiation and it may happened due to no agreeable SDP offer/answer between the 2 parties(e.g. codecs used, encryption policy, media type etc)

24018
Conference escalation is not supported by application
Conference escalation handling is not supported by the application

24019
Remote participant mismatch
Conversation identifier is already in use by a different remote participant

24020
Message Throttling is in effect
Platform has reached its throttling limit

24021
Conversation is terminating or terminated
Conversation is terminating or terminated

24022
Media type is already taken by another call
One or more media type(s) requested is already owned by another call in the conversation

24023
Decline due to presence
User’s current presence state does not allow incoming calls

24024
Call termination due to successful transfer
Call termination due to successful transfer

24025
No application handler for media type
Application cannot handle one or more media type(s) requested

24026
Call establishment timed out

24027
Conference invitation handling is not supported by the application
Conference invitation handling is not supported by the application

24028
Endpoint is in draining mode.
When draining Endpoint will not accept new conversations

24029
Message is not verified by endpoint
Endpoint determined that the incoming request should not processed due to verification failure

24030
No transaction handler
Endpoint is not registered for non INVITE transaction

24031
No transaction handler
Endpoint is not registered for INVITE transaction

24032
No component handler
Unable to retrieve component handler for a message inside dialog

24033
No component handler
Unable to retrieve component handler for a message outside dialog

24034
No message received handler
Application has not registered to handle incoming messages on the Endpoint

24035
Event header is missing in registration notify
Event header is missing in registration notify

24036
Endpoint is terminating or terminated
Endpoint is terminating or terminated

24037
Incoming Invite transaction timed out
Incoming Invite transaction timed out

24038
Incoming non-Invite transaction timed out
Incoming non-Invite transaction timed out

24039
No offer answer negotiator found
No offer answer negotiator found to handle incoming invite

24040
Request pending
Re-Invite collision

24041
No message received handler
Application has not registered to handle incoming messages on the Signaling Session

24042
No session received handler
Application has not registered to handle incoming signaling session

24043
Request is already terminated
Request is already terminated before being processed

24044
Bad content type
Content type in incoming message could not be parsed

24045
Null or empty content type
Content type is either null or empty

24046
Remote session is invalid
Session is being terminated internally because remote session does not have the session

24047
Session timer expired
Session is being terminated internally because session timed out waiting for a request or response

24048
Session connection timer expired
Session is being terminated internally because session connection timer expired

24049
Request received on bad call leg
Session is being terminated internally because request was received on bad call leg

24050
Session timer value is too small
Session timer value is too small

24051
Unable to create session
Unable to create session

24052
Incoming subscription is not supported
Platform does not support regular incoming subscriptions

24053
Event header is missing, cannot be parsed or is not supported
Event header is missing, cannot be parsed or is not supported

24054
Provisional acknowledgement does not match any pending provisionals
Provisional acknowledgement does not match any pending provisionals

24055
No dialog information found in the request
Unable to infer the dialog infromation from the request

24056
Extension method in the request is not supported
Extension method in the request is not supported

24057
No session refer received handler
Application has not registered to handle incoming refer on the signaling session

24058
Internal error occured
Internal error occured during processing this request

24059
Endpoint is already terminated
Endpoint cannot handle this request because it is already terminated

24060
Incoming message is badly formatted
Incoming message is badly formatted

24061
Route set recovery retries failed
All attempts to recover the route failed

24062
Joining the conference lobby is not supported
Joining the conference lobby is not supported

24063
Timed out while waiting in the lobby
Timed out while waiting in the lobby

24064
Escalation to a conference failed
Disconnected from the conference as the escalation process failed

24065
Re-establishing sessions with server
The existing conferencing sessions with the server are terminated to establish new sessions

24066
Unable to dial-in to the AVMCU
Unable to dial-in to the AVMCU

24067
Mcu is rolling over
Call was terminated because Mcu rollover was detected

24068
Acknowedgement wait operation timed out
Acknowledgement did not arrive within a specified time period

24069
Unsupported extension headers
Unsupported extension headers

24070
No escalation invitation in invite data
Unable to extract escalation invitation data from incoming INVITE request

24071
Escalation invitation has no ”available” or ”additional” media types
Escalation invitation has no ”available” or ”additional” media types

24072
Remote participant mismatch
Escalation invitation request has a remote participant mismatch

24073
Conversation state is not valid to perform escalation
Conversation state is not valid to perform escalation

24074
Call signaling session disconnected
Call signaling session disconnected.

24075
Call park operation failed
Call park operation failed.

24076
Call session is being terminated due to successful escalation
Call session is being terminated due to successful escalation

24077
Invalid MimeProcessor result
Incoming MIME parts were considered invalid

24078
Unsupported media types
One or more media types in the incoming invite is not supported

24079
Failed to parse incoming invite
Incoming invite parsing failed

24080
Conversation auto termination
Termination triggered by conversation auto termination

24081
Endpoint termination
Termination triggered by termination of endpoint

24082
Conference termination
Termination triggered by termination of conference

24083
Message was received out of dialog.
The message was received out of dialog.

24084
Unable to update conversation properties.
Conversation properties update failed. Property update can be retried at a later time.

24085
Application has not registered for call message received handler.
Application has not registered for call message received event handler.

24086
Call is terminating or terminated.
Call is currently in the process of terminating or it is already terminated.

24087
Message was not handled by the MCU proxy entity.
Proxy entity communicating with MCU has not registered event handler for incoming message.

24088
Media provider returned an invalid answer.
Invalid header or content type found in the answer from media provider.

24089
Media provider returned an invalid offer.
Invalid header or content type found in the offer from media provider.

24090
Initial offer answer exchange has not completed.
The initial negotiation of the media has not completed so cannot be changed at this time.

24091
Unable to find the call to replace based on the value from replaces header.
Unable to find the call to replace based on the value from replaces header.

24092
Call to be replaced does not support replaces capability.
Call to be replaced does not support replaces capability.

24093
Conference invitation is not supported by this endpoint.
Conference invitation is not supported by this endpoint.

24094
Conference invitation is not allowed in the current conversation state.
Conference invitation is not allowed in the current conversation state.

24095
Incoming invite type is not known.
Incoming invite type is niether a call nor a conference invitation.

24096
Unable to route the incoming invite to a valid conversation.
Unable to route the incoming invite to a valid conversation.

24097
Unexpected exception occured during processing of incoming invite.
Unexpected exception occured during processing of incoming invite.

24098
Outgoing Invite transaction timed out
Outgoing Invite transaction timed out

24099
SDP-less reinvite not supported
SDP-less reinvite not supported

24100
General diagnostic information.
General diagnostic information.

24101
Local additional diagnostics information
Additional diagnostics information from the local side when sending error report

24102
Remote side did not provide any diagnostics information.
Remote side did not provide any diagnostics information.

24103
Remote side did not provide any diagnostics information in the conference document.
Remote side did not provide any diagnostics information in the conference document.

24104
Refer request parsing failed.
Parsing of incoming REFER request failed.

24105
Refer request was received on a secondary session.
Refer request was received on a secondary session.

24106
Media was cancelled by user action.
Media was cancelled by user action.

24107
Conference invitation termination due to successful completion.
Conference invitation termination due to successful completion.

24108
Conference invitation accept failed.
Conference invitation accept failed.

24109
Conference invitation delivery failed.
Conference invitation delivery failed.

24110
Outbound conference invitation timer expired.
Outbound conference invitation timer expired.

24111
Session timer could not be refreshed because of an expected failure.
Session is being terminated internally because an expected failure was encountered during session timer refresh.

24112
No recognized available media types
Conference invitation contains no recognized available media types

24113
Call park accept operation failed.
Call park accept operation failed.

24114
Back to back call escalation failed.
Back to back call escalation failed.

24115
User does not want to be disturbed.
User does not want to be disturbed.

24116
The request was rejected because the application did not respond to the incoming call and it was not the preferred endpoint.
The request was rejected because the application did not respond to the incoming call and it was not the preferred endpoint.

24117
The get presence operation failed.
The get presence operation failed.

24118
Application accepts invitations via static registration only.
Application accepts invitations via static registration only.

24119
Application did not register an auto accept handler.
Application did not register an auto accept handler.

24120
Primary session is being terminated on successful back to back escalation.
Primary session is being terminated on successful back to back escalation.

24121
Primary session is being terminated prematurely before call escalation.
Primary session is being terminated prematurely before call escalation.

25000
Retrying via PSTN due to WAN outage

25001
Retrying via PSTN due to bandwidth congestion

25002
Routing to best pool

25003
Invalid or missing original request URI

25004
Pstn Retry Disallowed by policy

25005
Invalid from user voice Policy

25006
The callee’s primary pool failed to respond in a timely manner.
A call failed because the callee’s pool failed to respond.  This can happen if the pool is busy or was taken offline while the request was being processed. Administrators should check the events on the callee’s pool for potential load or capacity issues.  Administrators should also check the toplogy for potential network related errors.

25007
Attempt to route to Backup registrar timed out

25008
Attempting to route to Primary Pool

25009
Attempting to route to Backup Pool

25010
Primary Pool is currently unavailable

25011
Backup Pool is currently unavailable

25012
Unexpected ICR targeted request received

25013
An unexpected error occurred while dispatching the request to the Intercluster Routing application.
An unexpected error occurred while dispatching the request to the Intercluster Routing application. Administrators should look for events reported by ‘API module’ in the event log. Administrators can reference the diagnostic header reported with this code to determine which server generated the error.

25014
Attempt to route to Best pool timed out

25015
Unexpected error occured while processing the request

25016
Unexpected error occured while routing the request

25017
Unexpected error occured while processing a response

25018
Client transaction timed out

25019
Client transaction cancelled

25020
Client transaction Terminated

26000
Ms-App header missing
INVITE without Ms-App header was received.

26001
Wrong application type
INVITE with Ms-App header but invalid application type was received, i.e., not equal to ‘ans’.

26002
Invalid parameter
INVITE with Ms-App header and correct application type but with the wrong parameter, i.e., ID=GUID isn’t the first parameter.

26003
Invalid announcement ID
INVITE with Ms-App header and correct application type but unknown announcement ID.

26004
Announcement cannot be played
Audio file cannot be played and/or TTS failed.

26005
The Response Group application was unable to transfer the call to the configured destination and no fallback exists.
Users will experience failed calls as the Response Group application was unable to transfer the call to another endpoint. Administrators should check that the transfer destinations configured for the target workflow or queue are reachable.

26006
Cannot create new back to back session.
The connection between the caller and the agent through the RGS B2B failed.

26007
Audio modality terminated. Terminating IM call.
The voice call between the two remote parties is terminated. IM session is automatically disconnected.

26008
Supervised transfer not supported.
RGS as received an INVITE w/ replaces or a REFER with a replaces parameter encoded in the ReferTo header.

26009
Media type not available.
An IM call is received. No voice conversation exists.

26010
UA must support Replaces.
An INVITE without support for Replaces header has been rejected.

26011
Ms-Application-Aor missing.
INVITE without  Ms-Application-Aor header has been received.

26012
Cannot accept call with Ms-Sensitivity header set.
INVITE with a Ms-Sensitivity header has been rejected.

26013
Team call not supported.
INVITE with Ms-Routing-Scenario :Team.

26014
User not authorized to make outbound call on behalf of the Response Group.
The user has tried to make an outbound call using the identity of a Response Group he is not part of.

26015
User not authorized to make outbound call on behalf of the Response Group.
The user has tried to make an outbound call using the identity of a Response Group which doesn’t support anonymity.

26016
User not authorized to make outbound call on behalf of the Response Group.
The user has tried to make an outbound call using the identity of a Response Group, not present in AOR.

26017
Internal server error.
The server cannot handle the request because an internal error.

26018
No settings loaded for this Response Group yet.
The server cannot accept the audio video call because cannot find settings for this Response Group.

26019
Response Group settings found but is not active.
The server cannot accept the audio video call because this Response Group is not active.

26020
Certificate validation failed.
The server cannot accept the audio video call due to certificate validation failure.

26021
Too many simultanous calls.
The server cannot accept the audio video call because the simultanious calls number exceeded.

26022
Cannot accept conference call.
The server cannot accept conference call.

26023
Cannot accept call with video only SDP.
The server cannot accept call with video only SDP.

26024
Cannot accept call because of memory pressure.
The server cannot accept call because of the memory pressure.

26025
Blind transfer failed.
Blind transfer failed.

26026
Invite with replaces cannot be handled.
Invite with replaces is rejected because the caller has disconnected the call while the B2B is being created.

26027
Cannot accept call because invalid header found.
Call cannot be accepted because contains an invalid header.

26028
User not authorized to make outbound call on behalf of the Response Group to another Response Group.
The user has tried to make an outbound call using the identity of a Response Group, targeting another Response Group.

26029
Call is disconnected because of invalid configuration.
Call is disconnected because of invalid configuration.

27000
To-Uri Domain is not in the sender-tenant allow list
Cannot route to the destination user or conference domain because the To-URI domain is not configured in the sender-tenant domain allow list.

27001
To-Uri Domain is blocked by sender-tenant block list
Cannot route to the destination user or conference domain because the To-URI domain is explicitly blocked by the sender-tenant domain block list.

27002
From-Uri Domain is not in the receiver-tenant allow list
Cannot route to the destination user or conference domain because the From-URI domain is not configured in the receiver-tenant domain allow list.

27003
From-Uri Domain is blocked by receiver-tenant block list
Cannot route to the destination user or conference domain because the From-URI domain is explicitly blocked by the receiver-tenant domain block list.

27004
Unexpected IncomingFederation dispatch failure

27005
Unexpected OutgoingFederation dispatch failure

27006
Target domain doesn’t belong to a valid tenant.

27007
From domain doesn’t belong to a valid tenant.

27008
Failed to parse target-uri.

27009
Failed to parse from-uri.

27010
An unexpected exception occurred

28000
User is not SIP enabled.

28001
Internal error while processing Windows authentication or authorization.

28002
The phone number or extension is invalid.

28003
The pin is invalid.

28004
The phone number is ambiguous.

28005
The pin is not set.

28006
The pin is expired.

28007
The account is locked.

28008
The account is disabled.

28009
Internal error while processing pin authentication or authorization.

28010
Certificate negotiation failed.

28011
The certificate is expired.

28012
The certificate is invalid.

28013
The certificate is not found.

28015
Internal error while processing OCS-signed certificate authentication or authorization.

28016
User is not provisioned in this deployment.

28017
WsFed token signing key cannot be resolved.  Check that token is obtained from appropriate WsFed environment.

28018
WsFed token produced with incorrect site policy.

28019
Internal error while processing web ticket authentication or authorization.

28020
No valid security token.

28021
Unsupported security token type.

28022
No valid subject statement.

28023
No valid message security.

28024
Internal error when processing WsFed authentication or authorization.

28025
No valid security principal.

28026
No valid security identity.

28027
No valid message security.

28028
WsFed token transfer key cannot be resolved.  Check that token is obtained for this service in appropriate WsFed environment.

28029
Authentication type not allowed.

28030
Internal error while processing usernametoken authentication or authorization.

28031
Invalid web ticket request (RST).

28032
The web ticket is invalid.

28033
The web ticket has expired.

28034
Proof web tickets can be validated on any server in the topology so this error code is deprecated.

28035
The SIP URI in the claim type requirements of the web ticket request does not match the SIP URI associated with the presented credentials.

28036
The identity in the renewed ticket does not match presented credentials.

28037
The AppliesTo element of web ticket request points to a different web server or site.

28038
Unsupported token type in web ticket request.

28039
Unsupported key type in web ticket request.

28040
Invalid Timestamp element in security header.

28041
Timestamp is outside of allowed time skew range.

28042
Too many outstanding requests for a single user.

28043
Too many outstanding requests from anonymous users for a single conference.

28044
Too many outstanding requests for a single application.

28045
Internal throttling error.

28046
The password has expired.

28047
The account is disabled.

28048
The user is not signed in with WS Federation Passive credentials.

28049
WS Federation Passive credentials present but could not read. Trying silent authentication with existing credentials.

28050
WS Federation Passive ticket expired.

28051
WS Federation Passive ticket is not valid.

28052
Bad Gateway.

28053
Unexpected content-type from WCF proxy target.

28054
Internal Error in WCF proxy operation.

28055
The OAuth token is invalid.

28056
The OAuth token has expired.

28057
The OAuth token has invalid audience.

28058
The OAuth token has unknown tenant.

28059
The OAuth token has no user claims.

28060
The OAuth token is not valid for the trust level.

28061
Internal error while processing OAuth token authentication or authorization.

28062
The user’s tenant does not match the tenant from the OAuth token.

28063
WS Federation Passive ticket does not contain the required claims. Please contact administrator.

28064
Mutltiple users found in AD for given PUID/SID.

28065
Supplied conference URI is not valid.

28066
User has not been assigned to a home server in this deployment.

28067
Policy prevents request from being proxied.

28068
HTTP proxy is unable to communicate with the next hop.

28069
Internal Error in HTTP proxy operation.

28070
Service does not allow a cross domain request from this origin.

28071
The ticket presented could not be verified, a new ticket is required.

28072
The soap message received is invalid

29000
Mobility Service terminates a call
Mobility Service terminates a call

29100
Outside voice not enabled for this user
Outside voice not enabled for this user

29101
Simul-ring number does not match phone number
User simul-ring number does not match mobile phone number

29102
Teamcall does not reach mobile phone
Teamcall does not reach mobile phone

29103
Delegation does not reach mobile phone
Delegation does not reach mobile phone

29104
Simul-ring does not reach mobile phone
Simul-ring does not reach mobile phone

29105
Media type is not supported
Media type is not supported

29106
User declined invitation
User declined invitation

29107
Unknown incoming out of dialog INVITE for ApplicationEndpoint
Unknown incoming out of dialog INVITE for ApplicationEndpoint

29108
Mobility Service application endpoint can not handle INVITE without replace header
Mobility Service application endpoint can not handle INVITE without replace header

29109
Failed to establish back-to-back call for INVITE w/Replaces
Failed to establish back-to-back call for INVITE w/Replaces

29110
No conversation was found for INVITE w/Replaces
No conversation was found for INVITE w/Replaces

29111
Audio call was declined because of policy
Audio call was declined because of policy

29112
Failed to establish back-to-back call
Failed to establish back-to-back call

29113
Transfer to self failed
Transfer to self failed

29114
Call forwarded request failed
Call forwarded request failed

29115
Call was declined because caller and callee endpoints are same
Call was declined because caller and callee endpoints are same

29116
Call was declined because user was not available
Call was declined because user was not available

29117
Inbound outside voice call was declined
Inbound outside voice call was declined

29118
RGS call was declined
RGS call was declined

29300
An internal error occured
Mobility Service hits an internal error

29301
An internal error occured: b2b failed to establish
An internal error occured: b2b failed to establish

29302
An internal error occured: impersonation failed
An internal error occured: impersonation failed

30000
Success
PNCH delivered push notification successfully

30001
Push notification could not be delivered to the PNS
Push notification could not be delivered to the PNS by PNCH

30002
The Push notification queue for this application is full
The PNCH application queue is full for this application

30003
This message was sent with Bad Payload Format
This message was sent with Bad Payload Format

30004
This request contains an invalid device token
This request contains an invalid device token

30005
This device is currently unreachable
The device for which push was sent is currently not reachable

30006
This application has been uninstalled
The target application for which this push was sent has been uninstalled

30007
Push Notification synthetic transaction succeeded
Push Notification synthetic transaction succeeded

30008
Push Notification synthetic transaction failed
Push Notification synthetic transaction failed

31000
Publishing telemetry data.
UCWA is publishing telemetry data for conference or MCU join on behalf of the application.

31001
Simul-ring number does not match phone number
User simul-ring number does not match mobile phone number

31002
Teamcall does not reach mobile phone
Teamcall does not reach mobile phone

31003
Delegation does not reach mobile phone
Delegation does not reach mobile phone

31004
Simul-ring does not reach mobile phone
Simul-ring does not reach mobile phone

31005
Media type is not supported
Media type is not supported

31006
User declined invitation
User declined invitation

31007
Unknown incoming out of dialog INVITE for ApplicationEndpoint
Unknown incoming out of dialog INVITE for ApplicationEndpoint

31008
UCWA application endpoint can not handle INVITE without replace header
UCWA application endpoint can not handle INVITE without replace header

31009
Failed to establish back-to-back call for INVITE w/Replaces
Failed to establish back-to-back call for INVITE w/Replaces

31010
No conversation was found for INVITE w/Replaces
No conversation was found for INVITE w/Replaces

31011
Audio call was declined because of policy
Audio call was declined because of policy

31012
Failed to establish back-to-back call
Failed to establish back-to-back call

31013
Transfer to self failed
Transfer to self failed

31014
Call forwarded request failed
Call forwarded request failed

31015
Call was declined because caller and callee endpoints are same
Call was declined because caller and callee endpoints are same

31016
Call was declined because user was not available
Call was declined because user was not available

31017
Inbound outside voice call was declined
Inbound outside voice call was declined

31018
RGS call was declined
RGS call was declined

31019
UCWA server terminates a call
UCWA terminates a call

31020
Outside voice not enabled for this user
Outside voice not enabled for this user

31021
An internal error occured
UCWA hits an internal error

31022
An internal error occured: b2b failed to establish
An internal error occured: b2b failed to establish

31023
An internal error occured: impersonation failed
An internal error occured: impersonation failed

31024
Failed to get simultaneous ring number for user
Failed to get simultaneous ring number for user

31025
Pstn call to local party during first stage of outside voice call failed
Pstn call to local party during first stage of outside voice call failed

31026
Conference join via dialout failed for user
Conference join via dialout failed for user

31027
Target application is terminating.
Target application is terminating.

31028
The client did not respond to the invitation
The client did not respond to the invitation

31029
Call is terminated because it was moved to a derived conversation
Call is terminated because it was moved to a derived conversation

31030
The action was initiated by UCWA server.
The UCWA server initiated the response or other action and did not supply diagnostic information.

31031
The action was initiated by a UCWA application.
A UCWA application initiated the response or other action and did not supply diagnostic information.

31032
The user is now being hosted on another front end.
The user is now being hosted on a new front end either due to load balancing changes or a failure of a front end.

31033
The UCWA application was terminated due to inactivity.
UCWA was unable to process the request because it was previously terminated due to inactivity.

31034
The call has timed out and is falling back from VOIP to phone audio.
The call has timed out and is falling back from VOIP to phone audio.

31035
The request timed out because the web application did not respond.
The request timed out because the web application did not respond.

31036
The web application is not available to receive the call.
The web application is not available to receive the call.

31037
The message or session description (SDP) size was too large.
The message or session description (SDP) size was too large.

31038
Message delivery failed while mobile application was in the background.
Message delivery failed while mobile application was in the background.

31039
Negotiation of media failed.
Negotiation of media failed.

31040
Escalation is not supported with a derived conversation.
Escalation is not supported with a derived conversation.

31041
The current call was replaced by another call.
The current call was replaced by another call.

31042
The call was declined because the gateway’s too-soon timer expired.
The call was declined because the gateway’s too-soon timer expired.

31043
Unable to deliver push notification to mobile client.
Unable to deliver push notification to mobile client.

31044
Push notification was delivered to the mobile client successfully.
Push notification was delivered to the mobile client successfully.

31045
Unable to deliver push notification to mobile client due to payload content.
Unable to deliver push notification to mobile client due to payload content.

31046
Service temporarily unavailable during service recovery.
Service temporarily unavailable during service recovery.

31047
Invitation received through static registration could not be delivered to application’s endpoint.
Invitation received through static registration could not be delivered to application’s endpoint.

31048
Maximum concurrent session limit has been exceeded.
Maximum concurrent session limit has been exceeded. This results in a session being logged out automatically.

31049
A currently configured server or user level policy caused the operation to fail.
A currently configured server or user level policy caused the operation to fail.

31050
Access problems to the Exchange store are preventing HD photo retrieval.
Access problems to the Exchange store are preventing HD photo retrieval.

31051
Access problems to Exchange are preventing retrieval of search results.
Access problems to Exchange are preventing retrieval of search results.

31052
Access problems to the Exchange are preventing storage of missed messages.
Access problems to the Exchange are preventing storage of missed messages.

31053
Mobile video is disabled on 3G networks.
Mobile video is disabled on 3G networks.

31054
Call connected with phone audio.
Call connected with phone audio.

31055
Client accepted incoming call with Phone Audio.
Client accepted incoming call with Phone Audio.

31056
An exception was detected that was not expected.
An exception was detected that was not expected.

31057
Escalation offer request from client completed with a failure.
Escalation offer request from client completed with a failure.

31058
Third party call control is not supported.
Third party call control is not supported.

31059
The error was detected by UCWA server.
The UCWA server detected an error and submitted an error report.

31060
The error was detected by UCWA server.
The UCWA server detected an error and submitted an error report.

31061
Another device has accepted the call.
Another device has accepted the call.

31062
The application specified is not currently active to process the request.
The application specified is not currently active to process the request.

31063
Invitation was declined so that more active application with same phone number handles it.
Invitation was declined so that more active application with same phone number handles it.

31064
Diagnostics information about incoming invitation.
Diagnostics information about incoming invitation.

31065
The message or session description (SDP) was missing.
The message or session description (SDP) was missing.

31066
Declining the invite for endpoint transfer to prevent callback on the originating endpoint.
Declining the invite for endpoint transfer to prevent callback on the originating endpoint.

31067
Max event count per frame limit reached.
Max event count per frame limit reached. This limit should not be reached by legitimate clients. This denotes mis-behaving client behavior.

32000
No corresponding ImDialogContext for a call
No corresponding ImDialogContext for a call

32001
Media type is not text
Media type is not text

32002
No proxy is available
No proxy is available

32003
Meesage cannot be sent to a proxy
Unexpected send failure

32004
Outbound endpoint is not started yet
Outbound endpoint is not running

32005
The component is not registered
The component is not registered

32006
No connection is available to a proxy
No connection is available to a proxy

32007
Stream to a proxy is not ready
Stream to a proxy is not ready

32008
Writer queue is deallocated
Writer queue is deallocated

32009
Stream is disposed
Stream is disposed

32010
Stream IO exception
Stream IO exception

32011
Outgoing queue is disabled
Outgoing queue is disabled

32012
Xmpp Federation is disabled
Xmpp Federation is disabled

32013
External federated endpoint is not registered
External federated endpoint is not registered

32014
Invalid partner domain
Invalid partner domain

32015
Connection limit has been reached
Connection limit has been reached

32016
DNS cannot be resolved
DNS cannot be resolved

32017
Meesage cannot be sent to a federated partner
Unexpected send failure

32018
Processing failure for an incoming message
Processing failure for an incoming message

32019
Stream has been closed remotely
Stream has been closed remotely

32020
Cannot connect to a federated partner
The remote host is actively refusing a connection

32021
TLS negotiation failed
TLS negotiation failed

32022
Access denied
An attempt was made to access a socket in a way that is forbidden by its access permissions

32023
XMPP server-wide subscription limit reached.
The XMPP is too busy to accept additional subscriptions.

33000
Invalid language
Call is declined because the CAA CO language is not valid.

33001
No conference ID or language selection entered.
Call is disconnected because the user has not entered any conference ID or language selection.

33002
Three invalid conference IDs
Call is disconnected because the user has entered an invalid conference ID three times.

33004
Three invalid passcodes
Call is disconnected because the user has entered three times an invalid passcode.

33005
User authentication error
Authentication failed because the user has entered three times an invalid pin, but the call is not disconnected.

33006
Unexpected authentication error
Call is disconnected due to an unexpected error while authenticating the user.

33007
Holding pen time-out
Call is disconnected because of the holding pen time-out.

33009
Lobby time-out
Call is disconnected because of the lobby time-out.

33010
Leader has kicked out the user
Call is disconnected because a leader of the conference has kicked out the user from the lobby.

33012
Unexpected lobby error
Call is disconnected due to an unexpected error in the lobby.

33013
Time-out waiting for input
Call is disconnected due to input waiting timeout from the user.

33014
Connection error with another server or service when joining conference
Call is disconnected due to connection errors in the system. Additional details may be present in the event logs.

33015
Missing conference endpoint
No primary application endpoint found in AD to join the conference.

33016
Supervised transfer is not supported
Incoming call has a Replaces header set, which is not supported.

33017
Caller must support Replaces header
Incoming call does not support Replaces header.

33018
Call terminated by remote before conference ID state.
The caller has terminated the call before entering the conference ID state.

33019
Call terminated by remote before any conference ID was entered.
The caller has terminated the call before entering any conference ID.

33020
Call terminated by remote after one conference ID attempt.
The caller has terminated the call after entering a first invalid conference ID.

33021
Call terminated by remote after two conference ID attempts.
The caller has terminated the call after entering two invalid conference IDs.

33022
Call terminated by remote after three conference ID attempts.
The caller has terminated the call after entering three invalid conference IDs.

33023
Call terminated by remote before authentication.
The caller has terminated the call before attempting to authenticate.

33024
Call terminated by remote after one authentication attempt.
The caller has terminated the call after one failed authentication attempt.

33025
Call terminated by remote after two authentication attempts.
The caller has terminated the call after two failed authentication attempts.

33026
Call terminated by remote after three authentication attempts.
The caller has terminated the call after three failed authentication attempts.

33027
Call terminated by remote while in the lobby.
The caller has terminated the call while waiting in the lobby.

33028
Call terminated by remote while in the holding pen.
The caller has terminated the call while waiting in the holding pen.

33029
Call terminated by remote while transferring to another pool.
The caller has terminated the call while being transferred to another pool.

33030
Call terminated by remote while transferring to the conference.
The caller has terminated the call while being transferred to the conference.

33031
Successfully connected.
The synthetic transaction has succeeded.

33032
The incoming call for the primary CO is rejected.
The primary CO only handles transferred calls, any other requests are rejected.

33033
The transferred call has invalid parameters.
The incoming request contains invalid parameters in Referred-by, and the transfer cannot be completed.

33034
Ms-Application-Aor header is not valid.
A conferencing user was unable to join a conference due to a missing or invalid SIP header (MS-Application-Aor) during call transfer.  This should only occur due to a third party inter-op issue or due to a product defect.

33035
Remote has successfully joined the conference.
Transfer succeeded, remote has successfully joined the conference.

33036
Cannot transfer the call to the conference due to an AVMCU error.
The service cannot transfer the call to the conference. The AVMCU encountered an error while processing the request.

33037
Cannot transfer the call to the conference due to a focus error.
The service cannot transfer the call to the conference. The focus encountered an error while processing the request.

33038
Cannot transfer the call to another pool.
The service encountered an error while transferring the call to another pool.

33039
Call terminated by remote before any language was entered.
The caller has terminated the call before making a language selection.

33040
Call terminated by remote while joining the conference.
The caller has terminated the call while trying to join the conference.

33041
Call terminated by remote before any passcode was entered.
The caller has terminated the call before entering their passcode.

33042
Call terminated by remote while recording their name.
The caller has terminated the call while recording their name.

33043
Cannot resolve the conference ID due to an internal error.
The service encountered an error while trying to resolve the conference ID.

33044
Cannot determine passcode requirements due to an internal error.
The service encountered an error while trying to determine passcode requirements.

33045
Cannot accept call due to an internal error.
The service encountered an error while trying to accept a call.

33046
Cannot verify passcode due to an internal error.
The service encountered an error while trying to verify a passcode.

33047
Referred-By header is not valid or missing.
The incoming request does not contain a valid Referred-By header.

33048
Transfer to another pool was successful.
The call was transferred to another pool successfully.

33049
Transfer to an operator was successful.
The call was transferred to an opertor successfully.

33050
Cannot transfer the call to an operator.
The service encountered an error while transferring the call to an operator.

33051
Call terminated by remote before selecting leader authentication.
The caller has terminated the call before selecting leader authentication.

33052
Call terminated by remote before organizer authentication.
The caller has terminated the call before attempting to authenticate as the meeting organizer.

33053
Call terminated by remote after one organizer authentication attempt.
The caller has terminated the call after one failed authentication attempt as the meeting organizer.

33054
Call terminated by remote after two organizer authentication attempts.
The caller has terminated the call after two failed authentication attempts as the meeting organizer.

33055
Call terminated by remote after three organizer authentication attempts.
The caller has terminated the call after three failed authentication attempts as the meeting organizer.

33056
Unexpected organizer authentication error
An unexpected error occurred while verifying the organizer’s pin.

33057
Certificate error with another server or service when joining conference
Call is disconnected due to Certificate (TLS) errors in the system. Additional details may be present in the event logs.

33058
Timeout encountered while trying to join the conference
Call is disconnected because of timeout while getting into the conference. See TimeoutType for additional details.

33059
Cannot accept call due to bandwidth issues.
The call cannot be accepted due to bandwidth issues.

33060
Caller must allow REFER messages.
Incoming call does not allow REFER messages.

33061
Cannot retrieve conference properties due to an internal error.
The service encountered an error while trying to retrieve conference properties.

33062
The application is not trusted by Focus in its deployment.
The service was unauthorized to join a conference hosted in its own deployment.

33100
The call was terminated without specific diagnostic information.
The call was terminated without specific diagnostic information. Checking event-logs and traces for this service may provide additional details.

34000
Updating media routes failed.
Updating media routes failed.

34001
PVA unexpected error
PVA leaves the conference due to an unexpected error.

34002
GVA unexpected error
GVA leaves the conference due to an unexpected error.

34003
CAS unexpected error
CAS leaves the conference due to an unexpected error.

34004
No more subscription with Focus
Terminate audio call, since conference state updates will not be received.

34005
Cannot establish AV call. Time out.
Establishing AV call failed since time out was reached.

34006
Cannot establish AV call. Unexpected error.
Establishing AV call failed because of unexpected error.

34007
Cannot join conference.
Joining conference failed.

34008
Player cannot play audio.
Player cannot play audio.

34009
PVA call was terminated by CAS.
PVA terminated by CAS.

34010
GVA call was terminated by CAS.
GVA call was terminated by CAS.

34011
PVA call cannot be initialized while waiting for GVA.
PVA call cannot be initialized and start servicing due to a timeout while waiting for GVA to initialize.  PVA will retry without waiting for GVA.

34012
Call was terminated by remote party.
Call was terminated by remote party (AV MCU).

34013
Call was terminated by remote party.
Call was terminated by remote party (AV MCU).

34014
Call was terminated by remote party.
Call was terminated by remote party (AV MCU).

34015
No more subscription with AV MCU.
Terminate audio call, since conference state updates will not be received.

34016
Call was terminated by remote party and we could not re-establish.
Call was terminated by remote party (AV MCU) and we could not re-establish despite retries.

34017
Call was terminated by remote party and we could not re-establish.
Call was terminated by remote party (AV MCU) and we could not re-establish despite retries.

34018
CAS app-invite dialog with AV MCU was terminated by remote party.
CAS app-invite dialog with AV MCU was terminated by remote party.

35000
Orbit not found.
There is no parked call in the Call Park application for the received orbit. The call might have been retrieved or disconnected.

35001
An unknown error occurred.
An unknown error occurred.

35002
No orbits are available.
Call cannot be parked because all orbits are in use. Extend the orbit range and try again.

35003
Cannot unpark from outside of organization.
Unparking is permitted for users of the same organization only.

35004
Park request timeout occurred.
Timeout occurred when processing a park request.

35005
Error occurred when accessing Unified Communications Application Services (UCAS).
Error occurred when accessing a Unified Communications Application Services (UCAS) database. Verify the connection and database server.

35006
Double park attempt rejected.
Parking both parties of a call is not supported. Second park request is rejected.

35007
Park request failed. Cannot establish a connection between the Call Park application and the parkee.
The parkee could not be transferred to the Call Park application due to a failure establishing a connection between the Call Park application and the parkee. As a result, the park request failed.

35008
The Call Park application cannot understand the current version. You need to upgrade the client or Call Park application.
The Call Park application cannot understand the Ms-call-park protocol version. You need to upgrade the client or Call Park application.

35009
No orbit found in unpark request. Specify an orbit and try again.
Retrieve request was rejected because it does not contain an orbit. An INVITE request without an orbit is rejected with this error (for example, a direct call to the Call Park application using the Call Park application address of record (AOR)).

35010
Safe-retrieve failed. No matching parked call found.
No parked call on the Call Park application for the received orbit and dialog ID (that is, safe-retrieve). The call might have been retrieved already or disconnected.

35011
Cannot forward to parking server. Verify that network connections are functioning correctly.
Could not forward the retrieve request to the server that parked the call. Verify the network connections and load balancer.

35012
The server running the Call Park application cannot process new park requests at this time. Try again later.
The server running the Call Park application is currently preventing new connections and rejects new park requests.

35013
Terminating parkee call leg after successful transfer.
For successful retrieve, ringback, and fallback, the Call Park application ends the call leg with the parkee.

35014
Terminating dialog with parker.
After sending final status to parker, the Call Park application ends dialog with parker.

35015
Park time expired. Terminating parkee call leg.
The Call Park application ends the call leg with parkee if retrieve, ringback, and transfer to fallback are not successful after a given time.

35016
There is no valid internal conversation to park a call. You must restart the Call Park application.
All conversations are invalid. Cannot park a call. You must restart the Call Park application.

35017
Retrieve action failed since the parked call couldn’t be transferred.
The transfer request was rejected on the parkee side and the Call Park application is terminating the retriever call leg.

35018
Group Pickup parked call queue is full.
Too many calls are already parked on for this Group Pickup pickup group.

35019
Group Pickup database wrong version.
The Group Pickup database is the wrong version.  Check the server event logs for details.

35020
Failed to accept the retrieving call.
Failed to accept the retrieving call.

35021
REFER to retriever failed.
REFER to retriever failed.

36000
Audio Test Service completed the call succesfully.
Audio Test Service completed the call succesfully.

36001
Audio Test Service terminated unexpectly.
Audio Test Service terminated unexpectly.

36002
Audio Test Service terminated call due to hold operation triggered by the client.
Audio Test Service terminated call due to hold operation triggered by the client

36003
Audio Test Service terminated call because client does not support send and receive audio.
Audio Test Service terminated call because client does not support send and receive audio.

36004
Audio Test Service terminated call when client tried to transfer the call or is being added to a conference.
Audio Test Service terminated call when client tried to transfer the call or is being added to a conference.

36005
Audio Test Service terminated call because it cannot play a media file.
Audio Test Service terminated call because it cannot play a media file.

36006
Audio Test Service terminated call because it cannot record to a file.
Audio Test Service terminated call because it cannot record to a file.

37000
The Web Conferencing Server was unable to open the conference folder, as it is being used by another server
Exclusive rights to a conference are granted to only one server at a time.  Another Web Conferencing Server is hosting this conference.

51000
Call terminated by transferee on successful transfer
Call terminated by transferee on successful transfer

51001
Call terminated by transferor on successful transfer
Call terminated by transferor on successful transfer

51002
Callee is taking the call to conference
Callee is taking the call to conference

51003
Callee is doing a personal transfer
Callee is doing a personal transfer

51004
Action initiated by user
Action initiated by user

51005
Call was replaced
Call was replaced

51006
Deprecated – 4.0 – Call terminated on signout
Call terminated on signout

51007
Callee media connectivity diagnosis info
Callee media connectivity diagnosis info

51008
Deprecated – 4.0 – Call terminated on suspension
Call terminated on suspension

51009
Deprecated – 4.0 – Application sharing is stopping on role demotion
Application sharing is stopping on role demotion

51010
Deprecated – 4.0 – Currently processing an outgoing invite
Currently processing an outgoing invite

51011
Application sharing is stopping on resource closed
Application sharing is stopping on resource closed

51012
Caller timeout on no response
Caller timeout on no response

51013
Deprecated – 4.0 – Application sharing stopped because content sharing started
Application sharing stopped since content sharing started

51014
Deprecated – 4.0 – Ip address change
Ip address change

51015
Video is supported on different endpoint
Video can be added to conversation using other enpdoint

51016
Call terminated after successful transfer
Call terminated after successful transfer

51017
Call Identified as malicious by user
Call Identified as malicious by user

51018
Media Session terminated on switching to a new session
Media Session terminated on switching to a new session

51019
Conference session terminated due to no active modes in the conference
Conference session terminated due to no active modes in the conference

51020
Terminating the session as the application was launched
Terminating the session as the application was launched

51021
Terminating the session on call park
Terminating the session on call park

51022
Terminating the session on no action from the user
Terminating the session on no action from the user

51023
App Invite media Session is auto terminated
App Invite media Session is auto terminated

51024
Escalation to a conference failed
Escalation to a conference failed

51025
Media Session terminated because the corresponding UCC endpoint was shutdown
Media Session terminated because the corresponding UCC endpoint was shutdown

51026
Instant Message session is replaced by new session
Existing Instant Message session is terminated and replaced by a new session from the same remote participant.

51027
ConferenceJoinTimeMsecs
Indicates conference join time in milliseconds

51028
FocusJoinTimeMsecs
Indicates focus join time in milliseconds

51029
AVMCUJoinTimeMsecs
Indicates avmcu join time in milliseconds

52000
Currently not defined
Currently not defined

52001
Client side general processing error.
This is a catch all diagnostic code in client applications that indicates something unexpected happened.  This diagnostic may fire due to interoperability issues with third party applications or due to system resource issues such as high memory or CPU.  Administrators should contact third party developers, if a third party application appears to be the cause.  Otherwise, this issue is generally not actionable.

52002
Deprecated – 4.0 – Presence error
Presence error, may be DND

52003
Deprecated – 4.0 – Conference disabled by policy
Conference disabled by policy

52004
Mismatched conversation or conference id
Mismatched conversation or conference id

52005
Escalation cross over
Escalation cross over

52006
Escalation request from participant not in conversation
Escalation request from participant not in conversation

52007
Escalation request for non connected mode
Escalation request for non connected mode

52008
Content type is not correct
Content type is not correct

52009
Error parsing body
Error parsing body

52010
Reject the incoming dial out from MCU
Rejecting an incoming dial out request from MCU for a conference that the user is already connected to.

52011
Disabled by policy
Administrative server policy does not allow the use of this mode of communication.  Policy information is received by the client through inband provisioning.

52012
Deprecated – 4.0 – Devices not present
Devices not present

52013
Empty SDP invite
Empty SDP invite

52014
Cant create conversation window
Application sharing cannot be split in to another conversation window.

52015
Deprecated – 4.0 – Got incoming re-invite
Got incoming ReInvite while there is a pending outgoing ReInvite

52016
Current conversation is being escalated to conference
Current conversation is being escalated to conference

52017
Encryption levels dont match
Encryption levels dont match

52018
Do not disturb
Do not disturb

52019
Deprecated – 4.0 – Blocking scenario
Blocking scenario

52020
Blocked Contact
Contact blocked by user

52021
Call terminated on media timeout
The call was terminated because media stopped flowing after the media channel was established.  This could occur due to a network glitch or because a hop between the two endpoints is no longer reachable.

52022
This client is not the most active endpoint
This client is not the most active endpoint

52023
Deprecated – 4.0 – Caller timeout on no response
This diagnostic is sent by legacy clients when the caller does not receive a response from the remote party.  This can occur if the server is under load, the remote party is not enabled for voicemail, or because of product defect on the remote party’s side.

52024
Video only sessions are not supported
Video only sessions are not supported

52025
Audio mode disabled by policy
Audio mode disabled by policy

52026
Video mode disabled by policy
Video mode disabled by policy

52027
Deprecated – 4.0 – Audio device not available
The user is attempting to accept a call when no audio device has been configured.

52028
Video device not available
Video device not available

52029
Deprecated – 4.0 – One or more audio device is not configured
One or more audio device is not configured

52030
Webcam is not configured
Webcam is not configured – NOT CURRENTLY USED

52031
Call terminated on media connectivity failure
A media path could not be established between the two parties.  The most common cause for this is that a legacy client in the conversation needs to be patched (KB 2028888).  This could also happen due to configuration issues such as the Media Relay server being unreachable due to firewall misconfiguration, port range mismatch with internal servers or because of expired credentials.

52032
Requested operation is not supported for call on hold
Requested operation is not supported for call on hold

52033
Incoming conversations are blocked over federation link
Incoming conversations are blocked over federation link

52034
Rejected Duplicate call from PBX
Rejected Duplicate call from PBX

52035
This client has an IM session with the same conversation ID
This could happen when forwarding a call to another user, and the new user replies via IM.

52036
Audio is not configured
The user is attempting to accept a call when no audio device has been configured.

52037
The client has reached the max number of diagnostic records. No more will be reported for this call.
The client has reached the max number of diagnostic records. No more will be reported for this call.

52038
Putting outgoing call with early media on hold is not supported
The call was cancelled because the caller attempted to place the call on hold before it was accepted.  This commonly occurs when the caller accepts an incoming call before the outgoing call is established.

52039
The recipient is responding in another way, such as IM or phone.
This is a normal behavior where the user typically chooses to reject an audio call and instead reply via instant messaging.

52040
Call auto-rejected when paired
Call auto-rejected when paired

52041
Conversation context has unknown format
Conversation context has unknown format

52042
A new voice modality cannot be added to this conversation since another one already exists
This is typically a race condition when two users decide to escalate an instant messaging conversation to an audio call.  The issue occurs when both parties attempt to add audio at the same time.

52043
Call terminated on hold failure
The most common occurrence of this is when a user accepts a call while connected to voicemail as Exchange UM does not support hold.  This diagnostic indicates that a user accepted an incoming call or placed an outgoing call while another call was active.  The client application’s attempt to place the call on hold failed so the active call was terminated.

52044
Invitation for an application which is not installed
The application session invite was rejected as application is not installed.

52045
Application sharing modality already exists
A new application sharing modality could not be added to this conversation since another one already exists.

52046
Sharer has left the conference
The application sharing session has been terminated because no one is sharing anymore.  This is normal behavior.

52047
Deprecated – 4.0 – Video is supported on different endpoint
Video can be added to conversation using other enpdoint

52048
Escalation not allowed as a previous escalation request is still pending
The client application does not support adding multiple new modalities at the same time.  For example, a user is in an audio call and the remote party attempts to add video and application sharing at the same time.

52049
Leaving app sharing because re-invite failed
Leaving app sharing because re-invite failed

52050
File Type Disabled By Policy
The transfer of the file present in the offer is disallowed by policy

52051
Callee timeout on no response from caller
The callee sent a final response to the SIP INVITE but never received an ACK.  This could happen if the server drops the response or ACK.  Common causes for this include a race condition where a client is renewing its registration when a call is received or legacy clients using expired security associations.

52052
Audio not supported
Audio not supported

52053
Video not supported
Video not supported

52054
Replaced conversation or session not available
Replaces conversation or session not available

52055
Apply replaced conversation property failed
Apply replaced conversation property failed

52056
No supported modality exists
No supported modality exists

52057
On-behalf-of call auto-rejected due to deskphone pairing
On-behalf-of call auto-rejected due to deskphone pairing

52058
Duplicate secondary call
Duplicate secondary call

52059
Invalid SDP in response
The client application is unable to parse the SDP provided by the remote party.  This should only occur in third party interop scenarios.

52060
Session establishment pending
Session establishment pending

52061
Unsupported accept header
Unsupported accept header

52062
Unsupported required header
Unsupported required header

52063
Unsupported session description
Unsupported session description

52064
Invalid TO header
Invalid TO header

52065
Mismatched TO tag
This occurs when the client application receives a SIP INVITE with a To tag, but does not find a matching dialog.  This could indicate that a previous dialog was recently termianted.

52066
Replaced dialog not available
Replaced dialog not available

52067
The ringing timer has expired and this location is not the callee’s most active endpoint
When the ringing timer expires, the callee’s non-active endpoints will reject the incoming call with this diagnostic code.  If this diagnostic shows up as the aggregate summary of a call in CDR or the caller’s client logs, it indicates that the remote party’s most active endpoint failed to respond properly. This could occur if the active endpoint is non-responsive.

52068
Deprecated – 4.0 – Call terminated after successful transfer
Call terminated after successful transfer

52069
Failed to create audio video session
Failed to create audio video session

52070
User does not want to be disturbed
Incoming event rejected due to Source Network of the sender, Container Membership or Presence State

52071
URI host part mismatch
URI host part mismatch

52072
Deprecated – 4.0 – Call Identified as malicious by user
Call Identified as malicious by user

52073
Panoramic video without main not supported
This indicates a product defect where the calling user requests panoramic video without requesting video.

52074
Previous sign-out was abnormal
This is a client reported sign out event.  Administrators should look for commonly occurring HRESULT values in the diagnostic headers reported.  Common causes for this error include dropped wireless connections, servers entering maintenance mode and overloaded WANs in branch office scenarios.

52075
Local endpoint allocation failed
Local endpoint allocation failed

52076
Transfer target is being escalated to conference
Transfer target is being escalated to conference

52077
Invite with replace is not supported on hold
Invite with replace is not supported on hold.

52078
Invalid SDP in request
Invalid SDP in request

52079
Mediation Server Bypass Not Supported
Mediation Server Bypass Not Supported

52080
Cannot accept an incoming call from a paired device
Cannot accept an incoming call from a paired device

52081
Cannot perform the action when there is a re-INVITE pending
Cannot perform the action when there is a re-INVITE pending

52082
Session is detached from conversation
For instant messaging, this diagnostic indicates that the user was unable to join a scheduled meeting because audio has not been configured.  For audio or video, this indicates that a transfer was rejected because the party being transferred ended the call.

52083
Conversation terminated on connection error
The user lost network connectivity while attempting to place or receive a call.

52084
Fail to send response
Fail to send response

52085
Dialog does not exist
A SIP message is being sent on a signaling dialog that has been terminated.  If the message is an instant message, the client will attempt to re-establish the dialog to retransmit.  This diagnostic can commonly occur when two users end a conversation at the same time, or when one user sends an IM as the other user closes the conversation window.

52086
The conversation could not be established as the remote party is not available
The received response indicates that the remote party is not available, however presence shows the user as something other than offline.  Administrators should look at other diagnostic headers reported with individual calls to understand the exact cause.  This diagnostic may be reported for a variety of reasons, such as the remote client losing wireless or hanging.  It may also occur if the Exchange UM server serving an away user is offline or if a PSTN gateway returns a 480 response code.

52087
Failed to process response
Failed to process response

52088
Failed to refresh sessin timer
Failed to refresh sessin timer

52089
Caller failed to establish the session: remote party not responded in time or local message processing failed
This diagnostic indicates the caller received provisional responses but no final responses to its SIP INVITE.  This issue can occur if the remote party is in the process of renewing its registration when the invitation arrives.  It could also occur if the remote application is non-responsive.

52090
Invitation declined by user
The user receiving the invitation rejected the invitation by dismissing the toast notification.

52091
Instant Messaging disabled
The IM conversation cannot be established.  This typically occurs when the receiving user is on a device, such as a deskphone, which does not support IM.  It can also occur if instant messaging is explicitly disabled by policy or registry.

52092
The call was cancelled by the caller before the remote party answered
This is typically a normal behavior where a user hangs up after mis-dialing or hangs up because the remote party does not have voicemail.

52093
Conversation suspended due to a loss of network
The signaling session was terminated due to a loss of network.  This typically occurs when a wireless connection drops or a machine enters hibernation mode.  Audio calls will typically continue if audio is still flowing.  If the network dropped, the client will attempt to re-establish and send any queued instant messages once connectivity is restored.

52094
Instant Messaging conversation terminated on user inactivity
A timer fired indicating that the conversation was idle.  The client application is terminating the session to free up resources.  This is normal behavior.

52095
Media session terminated on internal client error
This is a catch all diagnostic in the client application layer.  It indicates that an internal error occurred which caused the conversation to be terminated.

52096
Application sharing is not supported
Application sharing is not supported

52097
Data sharing is not supported
Data sharing is not supported

52098
Transaction does not exist
Transaction does not exist

52099
Time out occurred while waiting for conference details
A user was unable to join a conference because the server failed to return conference details before a client side timer expired.  Administrators should check server and network performance to see where the SIP NOTIFY from the Front End Conferencing server was delayed.

52100
Resend request failed
Resend request failed

52101
Termination reason Not specified
The client application terminating the call did not provide diagnostic details to UCCAPI.  The application may be terminating the call for a normal or abnormal reason.  This is a catch-all diagnostic code.

52102
Currently process an outgoing invite
Currently process an outgoing invite

52103
Cannot launch the session application
Cannot launch the session application

52104
Cannot process the incoming transfer
Cannot process the incoming transfer

52105
Cannot accept the file transfer
Cannot accept the file transfer

52106
Another attempt will be made to connect
Another attempt will be made to connect

52107
Call terminated on signout
This is a normal behavior where calls are terminated because the user is signing out.

52108
Call terminated on suspension
Active conversations were suspended due to loss of network connectivity.  This typically occurs because of wireless drop or laptop hibernation.  The application will attempt to re-establish the conversations when connectivity is restored.

52109
Application sharing is stopping on role demotion
The current sharer was demoted by another presenter.  This causes the current sharing session to stop.  This is normal behavior.

52110
Application sharing stopped because content sharing started
Application sharing stopped since content sharing started

52111
Ip address change
Ip address change

52112
Callee did not receive an ACK for the 200 OK
The callee’s application sent a final SIP response but never received an ACK back.  This can occur if the client is in the process of renewing its registration when it responds.  In this case, the server might drop the callee’s response because the security associations being used are no longer valid.

52113
Client transaction does not exist
Client transaction does not exist

52114
Local bypassid doesn’t match the offerer’s
Bypass is enabled but the local bypassid does not match with the offerer’s

52115
Media network interface does not match bypass registration network interface
NIC allocated for Media does not match NIC used to register for bypassid

52116
Remote participant unavailable
Remote participant unavailable

52117
Instant Message dialog does not exist; please retry
Instant Message dialog does not exist; please retry

52118
Call terminated on media disconnected
Call terminated on media disconnected

52119
Conference join failed because a subscription channel could not be established
A user was unable to join a conference because a conference subscription received a failure response.  Administrators should check diagnostic headers in client side logs to determine why the SIP SUBSCRIBE was rejected.

52120
Rejecting invitation because another session exists in the same context
Rejecting invitation because another session exists in the same context

52121
Client is not completely signed-in causing incoming sessions to be rejected
Incoming invitations will be rejected if client is not completely recovered from resiliency mode.

52122
AddUser sent by client to focus/MCU failed
AddUser sent by client to focus/MCU failed

52123
No response received for message sent in the Instant Message sesion
Client time out due to no response received for message sent in the Instant Message sesion.

52124
The incoming request is bad because of missing or invalid headers or message body
The incoming request is bad because of missing or invalid headers or message body.

52125
No content type header in request
No content type header in request.

52126
The content type is not supported
The content type is not supported.

52127
Roaming session type does not match
Roaming session type does not match.

52128
Event header is not correct
Event header is not correct.

52129
The session is not connected yet
Reject the incoming message because the session is not connected yet.

52130
The internal transaction state does not match
The internal transaction state does not match.

52131
Message body is invalid
Message body is invalid.

52132
Reject incoming invite because there is a pending incoming invite
Reject incoming invite because there is a pending incoming invite.

52133
The method type is unknown or invalid
The method type is unknown or invalid.

52134
The request method is not allowed
The request method is not allowed.

52135
The sip version is not supported
The sip version is not supported.

52136
The request sequence number is corrupted
The request sequence number is corrupted.

52137
Unsupported sip header extension
Unsupported sip header extension.

52138
The content encoding header is not supported
The content encoding header is not supported.

52139
The peer to peer RDP session failed to establish correctly.
A user was unable to participate in an Application Sharing session because an RDP connection could not be established.

52140
Scenario B – Alternate call leg was accepted
Scenario B – Alternate call leg was accepted

52141
Conference session is not active in the conversation
Conference session is not active in the conversation

52142
Disconnect tpcp control channel
Disconnect tpcp control channel.

52143
Clear tpcp control channel due to call disconnected
Clear tpcp control channel due to call disconnected.

52144
Clear tpcp control channel due to redirect
Clear tpcp control channel due to redirect.

52145
SDP contains no compatible codecs
SDP contains no compatible codecs

52146
Reject incoming message because in this session message can only be sent out
Reject incoming message because in this session message can only be sent out.

52147
Different request has an existing CSEQ
Different request has an existing CSEQ.

52148
Drop incoming refer as incoming refers are disabled
Drop incoming refer as incoming refers are disabled.

52149
Decline incoming refer because it is in invalid state
Decline incoming refer because it is in invalid state.

52150
Refer operation is pending
Refer operation is pending.

52151
Transfer refer is not allowed for IM
Transfer refer is not allowed for IM.

52152
Some specific extension is not found in require or supported header
Some specific extension is not found in require or supported header.

52153
The expiring value is too small
The expiring value is too small.

52154
No or too many To tag
No or too many To tag.

52155
Monitor sharing ended due to resolution change.
Monitor sharing ended due to resolution change.

52156
Failed to start audio stream.
Failed to start audio stream.

52157
Tpcp controlling endpoint being disabled
Tpcp controlling endpoint being disabled.

52158
Failed to start video stream.
Failed to start video stream.

52159
Failed to start data stream.
Failed to start data stream.

52160
Cannot honor re-INVITEs from remote party to automatically start video when local user has not started video
Cannot honor re-INVITEs from remote party to automatically start video when local user has not started video

52161
Session was terminated as we are tearing down the conference due to failure on a different session
Session was terminated as we are tearing down the conference due to failure on a different session

52162
Appsharing session disconnected due to normal operations
An appsharing disconnect happened because RDP connection was shut down normally

52163
Appsharing session disconnected due to failures in RDP stack
An appsharing disconnect happened because of an internal processing error in the Lync Application Sharing component. Please refer to the error code followed by keyword “LyncAppSharingDebug”

52164
Appsharing session disconnected due to RDP stack closed the connection
An appsharing disconnect happened because Lync Application sharing closed the connection. This could be because of a protocol error or the sharer disconnected the viewer for other reasons

52165
Appsharing Session disconnected due to a connection failure in the RDP stack
Appsharing session disconnected occurred due to connection failure. In most cases, this is because viewer failed to connect in while executing the connection sequence protocol

52166
Appsharing session disconnected due to media stream dropping in media transport layer
An appsharing disconnect happened because appsharing media stream stopped due to RTP/RTCP connection drop in media transport layer

52167
call terminated for privacy reasons
Automatic call termination to avoid end user’s privacy violation – happens when another app starts rendering audio during a call

52168
Callee already in the invited conference.
Callee already in the invited conference.

52169
Cannot Connect to Exchange Server due to AutoD failures
Contains the Server that the client tried to connect to and the response

52170
cannot get user contacts from Exchange
Contains the Server that the client tried to connect to and the response

52171
Cannot get user contacts and no cache available, user sees empty contacts list
Contains the Server that the client tried to connect to and the response

53000
Insufficient Bandwidth Available
Failing because of insufficient bandwidth according to policy

53001
Candidates Restricted
Some ICE candidates were removed due to bandwidth limited by policy

54000
Connection to the Web Conferencing Server could not be established
The client was unable to establish a TLS connection with Web Conferencing Server or Web Conferencing Proxy.  Server configuration is a common cause

54001
Connection to the Web Conferencing Server could be established, but the server terminated immediately
The client was able to establish a connection with Web Conferencing Server or Proxy, but the server immediately closed the connection.  Server configuration is a common cause

54002
Web Conferencing Server unexpectedly terminated the connection
The server forcibly terminated the connection and might have sent a diagnostic message.  This is likely a product issue.

54003
The socket was unexpectedly closed without a break message
The socket was unexpectedly closed.  No close or break message was sent by server, and it was not a client-initiated action.  This happened after connection successfully completed.  Product issues or the server going down are common causes.

54004
Message processing error
The client encountered an unexpected error while processing a Web Confencing Server message.  This could mean that the client received unexpected data from the server, or there was a bug in processing the data.  Client terminated the connection.

54005
A resource was unable to be downloaded via HTTP
A resource was unable to be downloaded via HTTP.  Server IIS mis-configuration is a common cause.

54006
A resource was unable to be uploaded to the Web Conferencing Server
A content, image, or other resource was unable to be uploaded because server denied the request.  This can happen when a user runs out of space on the server, in one case.

54007
The certificate presented by the Web Conferencing Server or Proxy could not be validated.
The client could not validate the certificate presented by the server.  This can happen when the client does not have the proper root certificate trusted, or when a certificate has expired.

54008
The client was unable to convert a PowerPoint file so that it could be uploaded.
The client could not convert a PowerPoint file into a special format that can be uploaded and viewed by all clients.  This can happen when the client has a version of Microsoft Office without certain components installed or in case of product issues.

54009
Connection to the Web Conferencing Server in another topology could not be established
The client was unable to establish a TLS connection with Web Conferencing Server or Web Conferencing Proxy.  Server configuration is a common cause.  This happened on a different topology.

54010
Connection to the Web Conferencing Server in another topology could be established, but the server terminated immediately
The client was able to establish a connection with Web Conferencing Server or Proxy, but the server immediately closed the connection.  Server configuration is a common cause.  This happened on a different topology.

54011
Web Conferencing Server in another topology unexpectedly terminated the connection
The server forcibly terminated the connection and might have sent a diagnostic message.  This is likely a product issue.  This happened on a different topology.

54012
The socket for a connection to another topology was unexpectedly closed without a break message
The socket was unexpectedly closed.  No close or break message was sent by server, and it was not a client-initiated action.  This happened after connection successfully completed.  Product issues or the server going down are common causes.  This happened on a different topology.

54013
Message processing error
The client encountered an unexpected error while processing a Web Confencing Server message in another topology.  This could mean that the client received unexpected data from the server, or there was a bug in processing the data.  Client terminated the connection.  This happened on a different topology.

54014
A resource was unable to be downloaded via HTTP in another topology
A resource was unable to be downloaded via HTTP.  Server IIS mis-configuration is a common cause.  This happened on a different topology.

54015
A resource was unable to be uploaded to the Web Conferencing Server in another topology
A content, image, or other resource was unable to be uploaded because server denied the request.  This can happen when a user runs out of space on the server, in one case.  This happened on a different topology.

54016
The certificate presented by the Web Conferencing Server or Proxy in another topology could not be validated.
The client could not validate the certificate presented by the server.  This can happen when the client does not have the proper root certificate trusted, or when a certificate has expired.  This happened on a different topology.

54017
The legacy PowerPoint viewer failed to load.
The legacy PowerPoint viewer that is used when connecting to Wave14 meetings failed to load.  The client was unable to view the content as a result.

54018
The navigation to the WAC URL failed.
The attmept to navigate to the WAC URL failed.  The resulting code can either be an HTTP result (for example, a 404), or an HRESULT indicating a DNS failure or other internal HRESULT.  The client was unable to view the content as a result.

54019
The presentation at the WAC URL does not exist.
The client navigated to the WAC URL, but WAC returned an error indicating that there is no presentation at that URL.  This can happen if the presenter never initiated the WAC session, but should never happen.  The client was unable to view the content as a result.

54020
The WAC presentation failed with a critical error.
The WAC session has failed with a critical error.  The error message indicates the reason given to the client.  The client was unable to view the content as a result.

54021
The shared notes component failed.
The shared notes component failed to load in OneNote.

54022
The certificate presented by the WAC Server or Proxy could not be validated.
The client could not validate the certificate presented by the WAC server.  This can happen when the client does not have the proper root certificate trusted, or when a certificate has expired.

54023
The certificate presented by the WAC Server or Proxy could not be validated.
The client could not validate the certificate presented by the WAC server.  This can happen when the client does not have the proper root certificate trusted, or when a certificate has expired.  This happened on a different topology.

54024
A viewing URL navigation was attempted.
This tracks the number of times a WAC viewing URL is viewed.

54025
A viewing URL navigation was attempted.
This tracks the number of times a WAC viewing URL is viewed.  This happened on another topology.

54026
The legacy PowerPoint viewer failed to load.
The legacy PowerPoint viewer that is used when connecting to Wave14 meetings failed to load.  The client was unable to view the content as a result.  This happened on a different topology.

54027
The navigation to the WAC URL failed.
The attmept to navigate to the WAC URL failed.  The resulting code can either be an HTTP result (for example, a 404), or an HRESULT indicating a DNS failure or other internal HRESULT.  The client was unable to view the content as a result.  This happened on a different topology.

54028
The presentation at the WAC URL does not exist.
The client navigated to the WAC URL, but WAC returned an error indicating that there is no presentation at that URL.  This can happen if the presenter never initiated the WAC session, but should never happen.  The client was unable to view the content as a result.  This happened on a different topology.

54029
The WAC presentation failed with a critical error.
The WAC session has failed with a critical error.  The error message indicates the reason given to the client.  The client was unable to view the content as a result.  This happened on a different topology.

54030
The shared notes component failed.
The shared notes component failed to load in OneNote.  This happened on a different topology.

54031
The WAC presentation failed with a server error.
The WAC presentation failed because the server redirected the client to an error page.  This is usually the result of a misconfiguration.

54032
The WAC presentation failed with a server error.
The WAC presentation failed because the server redirected the client to an error page.  This is usually the result of a misconfiguration.  This happened on a different topology.

54033
The client was unable to convert a PowerPoint file so that it could be uploaded to support Lync 2010 clients.
The client could not convert a PowerPoint file into a special format that can be uploaded and viewed by Lync 2010 clients.  This can happen when the client has a version of Microsoft Office without certain components installed or in case of product issues.

54034
The navigation to the QnA URL failed.
The attmept to navigate to the QnA URL failed.  The resulting code can either be an HTTP result (for example, a 404), or an HRESULT indicating a DNS failure or other internal HRESULT.  The client was unable to view the content as a result.

54035
The certificate presented by the DMCU or Proxy for QnA content could not be validated.
The client could not validate the certificate presented by the DMCU server.  This can happen when the client does not have the proper root certificate trusted, or when a certificate has expired.

60000
Reserved

60999
Reserved

61000
Reserved

61999
Reserved

62000
Reserved

62999
Reserved

99880
Join Launcher Conference Information
This diagnostics code contains internal debug information for measuring join time.

99881
Join Launcher Conference Join Error – Invalid Meeting URL Format
Meeting URL format is invalid.

99882
Join Launcher Conference Join Error – Failed to find a matching domain for the incoming BaseURL
Meeting URL seems invalid. We didnt find a matching domain for the BaseURL specified

99883
Join Launcher Conference Join Error – Multiple matching tenants for this baseURL
Meeting URL maps to more than one tenant – not an expected scenario

99884
Join Launcher Conference Join Error – Lookup User failed
Looking up conference organizer failed

99885
Join Launcher Conference Join Error -Verify Conference failed
Conference Lookup has failed

99886
Join Launcher Conference Join Error – Could not find a matching regex to parse the incoming URL
The regular expression (Get-csWebServiceConfiguration -JoinIdentifierRegularExpression) is not applicable for this baseURL

99887
Join Launcher Conference Join Error : Conference verification timed out
Conference Verification with the Front end failed

99888
Join Launcher Conference Join Error : Server is overloaded
This JL server is overloaded. Rejecting any new requests

99999
Join Launcher Conference Join Error : Unknown error occurred
Totally unexpected issue where some HTTP context / headers were lost during request forward/proxy.