1xx – информационные ответы
SIP/2.0 100 Trying
Запрос обрабатывается.
SIP/2.0 180 Ringing
Местоположение вызываемого пользователя определено. Выдан сигнал о входящем вызове.
SIP/2.0 181 Call is Being Forwarded
Прокси-сервер переадресует вызов к другому пользователю.
SIP/2.0 182 Call is Queued
Вызываемый абонент временно недоступен. Вызов поставлен в очередь.
SIP/2.0 183 Session Progress
Используется для того, чтобы заранее получить описание сеанса информационного обмена от шлюзов на пути к вызываемому пользователю.
2xx – ответы о завершении запроса
SIP/2.0 200 OK
Успешное завершение.
SIP/2.0 202 Accepted
Запрос принят для обработки. Используется для справки о состоянии обработки.
3xx – сообщения о переадресации
SIP/2.0 300 Multiple Choices
Указывает несколько SIP-адресов, по которым можно найти вызываемого пользователя.
SIP/2.0 301 Moved Permanently
Вызываемый пользователь больше не находится по адресу, указанному в запросе.
SIP/2.0 302 Moved Temporarily
Пользователь временно сменил местоположение (настроена переадресация по SIPUA в т.ч. с VOIP-телефона).
SIP/2.0 305 Use Proxy
Вызываемый пользователь недоступен непосредственно. Входящий вызов должен пройти через прокси-сервер.
SIP/2.0 380 Alternative Service
Запрошенная услуга недоступна, но доступны альтернативные услуги.
4xx – невозможность обработать запрос
SIP/2.0 400 Bad Request
Запрос не распознан из-за синтаксических ошибок или ошибок в сигнализации.
SIP/2.0 401 Unauthorized
Нормальный ответ сервера о том, что пользователь еще не авторизовался. Обычно после этого абонентское оборудование отправляет на сервер новый запрос, содержащий логин и пароль.
SIP/2.0 401 AUTH Error: Stall nonce
1.Разные данные в поле NONCE (шифр пароля), проверить дату/время или проблема с протоколом шифрования
2. Проверить на клиентской стороне не заблокирован ли sipnet.ru (212.53.40.40)
3. Проверить в ВАТС статус присутствия. Должен быть «нет».
SIP/2.0 401 Expired Authorization
Время регистрации истекло.
SIP/2.0 402 Payment Required
Требуется оплата (зарезервирован для использования в будущем).
SIP/2.0 403 No Such User
Нет такого пользователя. Ошибка в номере, логине или пароле.
SIP/2.0 403 No license available
Кончились лицензия на SIP
SIP/2.0 403 You
Нет такого пользователя. Ошибка в номере, логине или пароле.
SIP/2.0 403 User Disabled
Пользователь отключен.
SIP/2.0 403 You do not have the required right
Неверный логин в поле «From»
SIP/2.0 403 Wrong Guess
Ошибка в пароле.
SIP/2.0 403 Conflict
Такой SIP-номер уже используется.
SIP/2.0 403 Forbidden
Абонент не зарегистрирован.
SIP/2.0 403 Empty Route Set
Нет ни одного шлюза в роутинге.
SIP/2.0 403 Caller Not Registered
Нет такого пользователя.
SIP/2.0 403 Out of Look-Ahead Retries
Перебор узлов закончен.
SIP/2.0 403 Invalid Phone Number
Нет такого направления.
SIP/2.0 403 No Money Left on RFC Account
На счету недостаточно денежных средств для совершения вызова.
SIP/2.0 404 Not found
Вызываемый абонент не найден, нет такого SIP-номера.
SIP/2.0 404 Undefined Reason
Неопределенное направление.
SIP/2.0 404 Unknown user account
Логин и пароль не найдены.
SIP/2.0 404 Out of Order
В заявке на маршрутизацию по этому направлению нет принимающих шлюзов.
SIP/2.0 405 Method Not Allowed
Метод не поддерживается. Может возникать если пользователь пытается отправлять голосовую почту и т.п.
SIP/2.0 406 No codecs match
Неправильная конфигурация кодеков.
SIP/2.0 406 Not Acceptable
Пользователь недоступен.
SIP/2.0 407 Proxy Authentication Required
Необходима аутентификация на прокси-сервере.
SIP/2.0 407 User not found
Проверить ID на CGP
SIP/2.0 408 Request Timeout
Время обработки запроса истекло. Абонента не удалось найти за отведенное время. (Проблема с firewall, нет ответа на Invite от сервера)
SIP/2.0 408 Login timed out
За отведенное время не получен ответ от сервера на запрос авторизации.
SIP/2.0 410 No Route
Вариант «SIP/2.0 403 Empty Route Set». Нет доступа к ресурсу или ресурс по указанному адресу больше не существует.
SIP/2.0 413 Request Entity Too Large
Размер запроса слишком велик для обработки на сервере.
SIP/2.0 415 No Media
Звонок совершается неподдерживаемым кодеком.
SIP/2.0 416 Unsupported Scheme
Сервер не может обработать запрос из-за того, что схема адреса не распознана.
SIP/2.0 420 Bad extension
Неизвестное расширение. Сервер не распознал расширение протокола SIP.
SIP/2.0 421 Extension Required
В заголовке запроса не указано, какое расширение сервер должен применить для его обработки.
SIP/2.0 423 Interval Too Brief
Сервер отклоняет запрос, так как время действия ресурса короткое.
SIP/2.0 480 Invalid Phone Number
Неправильный номер телефона, не соответствует количеству цифр или неправильный код страны или города.
SIP/2.0 480 Destination Not Found In Client Plan
Нет направления в тарифном плане абонента.
SIP/2.0 480 Wrong DB Response
Проблемы с центральной базой данных.
SIP/2.0 480 DB Timeout
Проблемы с центральной базой данных.
SIP/2.0 480 Database Error
Проблемы с центральной базой данных.
SIP/2.0 480 Codec Mismatch
Несоответствие кодеков.
SIP/2.0 480 No Money Left on RFC Account
Недостаточно денежных средств на счету.
SIP/2.0 480 Empty Route Set
Пустое направление. Нет принимающих шлюзов.
SIP/2.0 480 No money left
Недостаточно денежных средств на счету.
SIP/2.0 480 Temporarily Unavailable
Временно недоступное направление. (Возможно статус DND)
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Действие не выполнено. Нормальный ответ при поступлении дублирующего пакета.
SIP/2.0 482 Loop Detected
Обнаружен замкнутый маршрут передачи запроса.
SIP/2.0 483 Too Many Hops
Запрос на своем пути прошел через большее число прокси-серверов, чем разрешено.
SIP/2.0 484 Address Incomplete
Принят запрос с неполным адресом.
SIP/2.0 485 Ambiguous
Адрес вызываемого пользователя неоднозначен.
SIP/2.0 486 Busy Here
Абонент занят.
SIP/2.0 487 Request Terminated
Запрос отменен. Обычно приходит при отмене вызова.
SIP/2.0 488 Codec Mismatch
Нет шлюзов с поддержкой заказанного кодека.
SIP/2.0 488 Private IP Address
Адрес RTP media из сетей RFC1918.
SIP/2.0 488 Not acceptable here
Не совпадают кодеки
SIP/2.0 491 Request Pending
Запрос поступил в то время, когда сервер еще не закончил обработку другого запроса, относящегося к тому же диалогу.
SIP/2.0 493 Undeciperable
Сервер не в состоянии подобрать ключ дешифрования. Невозможно декодировать тело S/MIME сообщения.
SIP/2.0 499 Codec Mismatch
Отсутствует кодек.
5xx – ошибки сервера
SIP/2.0 500 Internal Server Error
Внутренняя ошибка сервера.
SIP/2.0 500 DB Timeout
Нет ответа от базы данных.
SIP/2.0 500 Database Error
То же самое, но в другой момент.
SIP/2.0 500 Wrong DB Response
Неправильный ответ базы данных.
SIP/2.0 500 Undefined Reason
Неопределенная причина.
SIP/2.0 500 account has been moved to a remote system
Аккаунт перенесен в удаленную систему (дословно).
SIP/2.0 500 Call placing quota exceeded
Превышен CPS.
SIP/2.0 501 Method Not Supported Here
В сервере не реализованы какие-либо функции, необходимые для обслуживания запроса. Метод запроса SIP не поддерживается.
SIP/2.0 502 Bad Gateway
Сервер, функционирующий в качестве шлюза или прокси-сервера, принимает некорректный ответ от сервера, к которому он направил запрос.
SIP/2.0 503 Service Unavailable
Сервер не может в данный момент обслужить вызов вследствие перегрузки или проведения технического обслуживания.
SIP/2.0 504 Server time-out
Сервер не получил ответа в течение установленного промежутка времени от сервера, к которому он обратился для завершения вызова.
SIP/2.0 505 SIP Version not supported
Версия не поддерживается. Сервер не поддерживает эту версию протокола SIP.
SIP/2.0 513 Message too big
Сервер не в состоянии обработать запрос из-за большой длины сообщения.
6xx – глобальная ошибка
SIP/2.0 600 Busy everywhere
Вызываемый пользователь занят и не желает принимать вызов в данный момент.
SIP/2.0 603 Decline
Вызываемый пользователь не желает принимать входящие вызовы, не указывая причину отказа.
SIP/2.0 604 Does Not Exist Anywhere
Вызываемого пользователя не существует.
SIP/2.0 606 Not Acceptable
Соединение с сервером было установлено. Отдельные параметры, такие как тип запрашиваемой информации, полоса пропускания, вид адресации не доступны.
I am new to MjSip and I use MjUa for creating a client. I want to connect to a asterisk server. it support G.711 but I can not config my app.
I use this config:
media=audio 4000 rtp/avp {audio 0 PCMU 8000 160, audio 8 PCMA 8000 160}
but i still get 488 error
please help me. how change «MjUa» config file?
here is all message log:
INVITE sip:57@192.168.0.254:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.57:5060;rport;branch=z9hG4bK2bfdff77
Max-Forwards: 70
To: "Alice" <sip:57@192.168.0.254:5060>
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
Call-ID: 728007708208@192.168.0.57
CSeq: 1 INVITE
Contact: <sip:157@192.168.0.57>
Expires: 3600
User-Agent: mjsip 1.7
Content-Length: 141
Content-Type: application/sdp
v=0
o=157 0 0 IN IP4 192.168.0.57
s=-
c=IN IP4 192.168.0.57
t=0 0
m=audio 4000 rtp/avp 0 8
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
-----End-of-message-----
1365314026097: 10:23:46.097 Sun 07 Apr 2013, 192.168.0.254:5060/udp (519 bytes) received
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK2bfdff77;received=192.168.0.57;rport=5060
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
To: "Alice" <sip:57@192.168.0.254:5060>;tag=as3f160681
Call-ID: 728007708208@192.168.0.57
CSeq: 1 INVITE
Server: FPBX-2.8.1(1.8.11.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6e640e9a"
Content-Length: 0
-----End-of-message-----
1365314026107: 10:23:46.107 Sun 07 Apr 2013, 192.168.0.254:5060/udp (326 bytes) sent
ACK sip:57@192.168.0.254:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.57:5060;rport;branch=z9hG4bK2bfdff77
Max-Forwards: 70
To: "Alice" <sip:57@192.168.0.254:5060>;tag=as3f160681
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
Call-ID: 728007708208@192.168.0.57
CSeq: 1 ACK
User-Agent: mjsip 1.7
Content-Length: 0
-----End-of-message-----
1365314026151: 10:23:46.151 Sun 07 Apr 2013, 192.168.0.254:5060/udp (706 bytes) sent
INVITE sip:57@192.168.0.254:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.57:5060;rport;branch=z9hG4bK644461b7
Max-Forwards: 70
To: "Alice" <sip:57@192.168.0.254:5060>
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
Call-ID: 728007708208@192.168.0.57
CSeq: 2 INVITE
Contact: <sip:157@192.168.0.57>
Expires: 3600
User-Agent: mjsip 1.7
Authorization: Digest username="157", realm="asterisk", nonce="6e640e9a", uri="sip:57@192.168.0.254:5060", algorithm=MD5, response="84ff5e12b8325a153e09ac2e316f5b1f"
Content-Length: 141
Content-Type: application/sdp
v=0
o=157 0 0 IN IP4 192.168.0.57
s=-
c=IN IP4 192.168.0.57
t=0 0
m=audio 4000 rtp/avp 0 8
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
-----End-of-message-----
1365314026152: 10:23:46.152 Sun 07 Apr 2013, 192.168.0.254:5060/udp (450 bytes) received
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK644461b7;received=192.168.0.57;rport=5060
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
To: "Alice" <sip:57@192.168.0.254:5060>;tag=as3f160681
Call-ID: 728007708208@192.168.0.57
CSeq: 2 INVITE
Server: FPBX-2.8.1(1.8.11.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
-----End-of-message-----
1365314026155: 10:23:46.155 Sun 07 Apr 2013, 192.168.0.254:5060/udp (326 bytes) sent
ACK sip:57@192.168.0.254:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.57:5060;rport;branch=z9hG4bK644461b7
Max-Forwards: 70
To: "Alice" <sip:57@192.168.0.254:5060>;tag=as3f160681
From: "aziz" <sip:157@192.168.0.254>;tag=350164683297
Call-ID: 728007708208@192.168.0.57
CSeq: 2 ACK
User-Agent: mjsip 1.7
Content-Length: 0
-----End-of-message-----
SIP ошибки и их значение
SIP/2.0 400 Bad Request — ошибка в сигнализации, скорее всего что-то с настройками оборудования
SIP/2.0 401 Unauthorized — нормальный ответ сервера о том, что пользователь еще неавторизировался, обычно после этого на абонентское оборудование отправляет на сервер логин и пароль
SIP/2.0 401 Expired Authorization — время регистрации истекло
SIP/2.0 403 No Such User — нет такого пользователя, ошибка в номере, логине или пароле
SIP/2.0 403 User Disabled — пользователь отключен
SIP/2.0 403 Wrong Guess — ошибка в пароле
SIP/2.0 403 Forbidden — абонент не зарегистрирован
SIP/2.0 403 Empty Route Set — нет ни одного шлюза в роутинге
SIP/2.0 403 Caller Not Registered — нет такого пользователя
SIP/2.0 403 Out of Look-Ahead Retries — перебор узлов закончен
SIP/2.0 403 Invalid Phone Number — нет такого направления
SIP/2.0 404 Not found — вызываемый абонент не найден, нет такого SIP-номера
SIP/2.0 404 Undefined Reason — неопределенное направление
SIP/2.0 404 Unknown user account — логин и пароль не найдены
SIP/2.0 405 Method Not Allowed — метод не поддерживается, может возникать если пользователь пытается отправлять голосовую почту и т.п.
SIP/2.0 406 No codecs match — неправильная конфигурация кодеков
SIP/2.0 406 Not Acceptable
SIP/2.0 407 Proxy Authentication Required — что-то с регистрацией
SIP/2.0 408 Request Timeout — превышение ожижание ответа на запрос
SIP/2.0 408 Login timed out — за отведенное время не получен ответ от сервера на запрос авторизации
SIP/2.0 410 No Route — вариант SIP/2.0 403 Empty Route Set
SIP/2.0 415 No Media — несоответствие кодеков
SIP/2.0 480 Invalid Phone Number — неправильный номер телефона
SIP/2.0 480 Destination Not Found In Client Plan — направления не существует
SIP/2.0 480 Codec Mismatch — несоответствие кодеков
SIP/2.0 480 Empty Route Set — что-то с маршрутизацией
SIP/2.0 480 No money left — недостаточно денег на счете
SIP/2.0 480 Temporarily Unavailable — временно недоступное направление — попробуйте позвонить позже
SIP/2.0 481 Call Leg/Transaction Does Not Exist — действие не выполнено, нормальный ответ при поступлении дублирующего пакета
SIP/2.0 487 Request Terminated — запрос отменен, обычно приходит при отмене вызова
SIP/2.0 486 Busy Here — абонент занят
SIP/2.0 488 Codec Mismatch — нет шлюзов с поддержкой заказанного кодека
SIP/2.0 488 Private IP Address — адрес RTP media из сетей RFC1918
SIP/2.0 499 Codec Mismatch — отсутствует кодек
SIP/2.0 500 Internal Server Error — внутренняя ошибка сервера
SIP/2.0 500 DB Timeout — нет ответа от базы данных
SIP/2.0 500 Database Error — то же самое, но в другой момент
SIP/2.0 500 Wrong DB Response — неправильный ответ базы данных
SIP/2.0 500 Undefined Reason — неопределенная причина
SIP/2.0 500 account has been moved to a remote system — аккаунт перенесен в удаленную систему (дословно)
SIP/2.0 5хх — проблемы с SoftSwitch-ом
SIP/2.0 603 Decline — отказ в обслуживании звонка
Читайте другие страницы сайта.
<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLi callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off
v=0
o=FreeSWITCH 1453086816 1453086817 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 30020 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 30020 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 33783cca-387a-1234-798b-002590e5052c
Found peer ‘M_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101
<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK0gvvQyg961BjS;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
<————>
Scheduling destruction of SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)
<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0
<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ Method: ACK
<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off
v=0
o=FreeSWITCH 1453097848 1453097849 IN IP4 193.27.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 18988 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 18988 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337bce93-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101
<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK1SNNSS1c4a24m;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
<————>
Scheduling destruction of SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)
<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0
<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ Method: ACK
<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK22eeUmjg1KrQg
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=05Ut47D2rF6mQ
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337f7865-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off
v=0
o=FreeSWITCH 1453088024 1453088025 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 28812 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 28812 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337f7865-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101
From Wikipedia, the free encyclopedia
The Session Initiation Protocol (SIP) is a signalling protocol used for controlling communication sessions such as Voice over IP telephone calls. SIP is based on request/response transactions, in a similar manner to the Hypertext Transfer Protocol (HTTP). Each transaction consists of a SIP request (which will be one of several request methods), and at least one response.[1]: p11
SIP requests and responses may be generated by any SIP user agent; user agents are divided into clients (UACs), which initiate requests, and servers (UASes), which respond to them.[1]: §8 A single user agent may act as both UAC and UAS for different transactions:[1]: p26 for example, a SIP phone is a user agent that will be a UAC when making a call, and a UAS when receiving one. Additionally, some devices will act as both UAC and UAS for a single transaction; these are called Back-to-Back User Agents (B2BUAs).[1]: p20
SIP responses specify a three-digit integer response code, which is one of a number of defined codes that detail the status of the request. These codes are grouped according to their first digit as «provisional», «success», «redirection», «client error», «server error» or «global failure» codes, corresponding to a first digit of 1–6; these are expressed as, for example, «1xx» for provisional responses with a code of 100–199.[1]: §7.2 The SIP response codes are consistent with the HTTP response codes, although not all HTTP response codes are valid in SIP.[1]: §21
SIP responses also specify a «reason phrase», and a default reason phrase is defined with each response code.[1]: §7.2 These reason phrases can be varied, however, such as to provide additional information[1]: §21.4.18 or to provide the text in a different language.[1]: §20.3
The SIP response codes and corresponding reason phrases were initially defined in RFC 3261.[1] That RFC also defines a SIP Parameters Internet Assigned Numbers Authority (IANA) registry to allow other RFC to provide more response codes.[1]: §27 [2]
This list includes all the SIP response codes defined in IETF RFCs and registered in the SIP Parameters IANA registry as of 27 January 2023. This list also includes SIP response codes defined in obsolete SIP RFCs (specifically, RFC 2543), which are therefore not registered with the IANA; these are explicitly noted as such.
SIP responses may also include an optional Warning header, containing additional details about the response. The Warning contains a separate three-digit code followed by text with more details about the warning.[1]: §20.43 The current list of official warnings is registered in the SIP Parameters IANA registry.
1xx—Provisional Responses[edit]
- 100 Trying
- Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response.[1]: §21.1.1
- 180 Ringing
- Destination user agent received INVITE, and is alerting user of call.[1]: §21.1.2
- 181 Call is Being Forwarded
- Servers can optionally send this response to indicate a call is being forwarded.[1]: §21.1.3
- 182 Queued
- Indicates that the destination was temporarily unavailable, so the server has queued the call until the destination is available. A server may send multiple 182 responses to update progress of the queue.[1]: §21.1.4
- 183 Session Progress
- This response may be used to send extra information for a call which is still being set up.[1]: §21.1.5
- 199 Early Dialog Terminated
- Can be used by User Agent Server to indicate to upstream SIP entities (including the User Agent Client (UAC)) that an early dialog has been terminated.[3]
2xx—Successful Responses[edit]
- 200 OK
- Indicates that the request was successful.[1]: §21.2.1
- 202 Accepted
- Indicates that the request has been accepted for processing, but the processing has not been completed.[4]: §7.3.1 [5] Deprecated.[6]: §8.3.1 [2]
- 204 No Notification
- Indicates the request was successful, but the corresponding response will not be received.[7]
3xx—Redirection Responses[edit]
- 300 Multiple Choices
- The address resolved to one of several options for the user or client to choose between, which are listed in the message body or the message’s Contact fields.[1]: §21.3.1
- 301 Moved Permanently
- The original Request-URI is no longer valid, the new address is given in the Contact header field, and the client should update any records of the original Request-URI with the new value.[1]: §21.3.2
- 302 Moved Temporarily
- The client should try at the address in the Contact field. If an Expires field is present, the client may cache the result for that period of time.[1]: §21.3.3
- 305 Use Proxy
- The Contact field details a proxy that must be used to access the requested destination.[1]: §21.3.4
- 380 Alternative Service
- The call failed, but alternatives are detailed in the message body.[1]: §21.3.5
4xx—Client Failure Responses[edit]
- 400 Bad Request
- The request could not be understood due to malformed syntax.[1]: §21.4.1
- 401 Unauthorized
- The request requires user authentication. This response is issued by UASs and registrars.[1]: §21.4.2
- 402 Payment Required
- Reserved for future use.[1]: §21.4.3
- 403 Forbidden
- The server understood the request, but is refusing to fulfill it.[1]: §21.4.4 Sometimes (but not always) this means the call has been rejected by the receiver.
- 404 Not Found
- The server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request.[1]: §21.4.5
- 405 Method Not Allowed
- The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI.[1]: §21.4.6
- 406 Not Acceptable
- The resource identified by the request is only capable of generating response entities that have content characteristics but not acceptable according to the Accept header field sent in the request.[1]: §21.4.7
- 407 Proxy Authentication Required
- The request requires user authentication. This response is issued by proxies.[1]: §21.4.8
- 408 Request Timeout
- Couldn’t find the user in time. The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time. The client MAY repeat the request without modifications at any later time.[1]: §21.4.9
- 409 Conflict
- User already registered.[8]: §7.4.10 Deprecated by omission from later RFCs[1] and by non-registration with the IANA.[2]
- 410 Gone
- The user existed once, but is not available here any more.[1]: §21.4.10
- 411 Length Required
- The server will not accept the request without a valid Content-Length.[8]: §7.4.12 Deprecated by omission from later RFCs[1] and by non-registration with the IANA.[2]
- 412 Conditional Request Failed
- The given precondition has not been met.[9]
- 413 Request Entity Too Large
- Request body too large.[1]: §21.4.11
- 414 Request-URI Too Long
- The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.[1]: §21.4.12
- 415 Unsupported Media Type
- Request body in a format not supported.[1]: §21.4.13
- 416 Unsupported URI Scheme
- Request-URI is unknown to the server.[1]: §21.4.14
- 417 Unknown Resource-Priority
- There was a resource-priority option tag, but no Resource-Priority header.[10]
- 420 Bad Extension
- Bad SIP Protocol Extension used, not understood by the server.[1]: §21.4.15
- 421 Extension Required
- The server needs a specific extension not listed in the Supported header.[1]: §21.4.16
- 422 Session Interval Too Small
- The received request contains a Session-Expires header field with a duration below the minimum timer.[11]
- 423 Interval Too Brief
- Expiration time of the resource is too short.[1]: §21.4.17
- 424 Bad Location Information
- The request’s location content was malformed or otherwise unsatisfactory.[12]
- 425 Bad Alert Message
- The server rejected a non-interactive emergency call, indicating that the request was malformed enough that no reasonable emergency response to the alert can be determined.[13]
- 428 Use Identity Header
- The server policy requires an Identity header, and one has not been provided.[14]: p11
- 429 Provide Referrer Identity
- The server did not receive a valid Referred-By token on the request.[15]
- 430 Flow Failed
- A specific flow to a user agent has failed, although other flows may succeed. This response is intended for use between proxy devices, and should not be seen by an endpoint (and if it is seen by one, should be treated as a 400 Bad Request response).[16]: §11.5
- 433 Anonymity Disallowed
- The request has been rejected because it was anonymous.[17]
- 436 Bad Identity-Info
- The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced.[14]: p11
- 437 Unsupported Certificate
- The server was unable to validate a certificate for the domain that signed the request.[14]: p11
- 438 Invalid Identity Header
- The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature.[14]: p12
- 439 First Hop Lacks Outbound Support
- The first outbound proxy the user is attempting to register through does not support the «outbound» feature of RFC 5626, although the registrar does.[16]: §11.6
- 440 Max-Breadth Exceeded
- If a SIP proxy determines a response context has insufficient Incoming Max-Breadth to carry out a desired parallel fork, and the proxy is unwilling/unable to compensate by forking serially or sending a redirect, that proxy MUST return a 440 response. A client receiving a 440 response can infer that its request did not reach all possible destinations.[18]
- 469 Bad Info Package
- If a SIP UA receives an INFO request associated with an Info Package that the UA has not indicated willingness to receive, the UA MUST send a 469 response, which contains a Recv-Info header field with Info Packages for which the UA is willing to receive INFO requests.[19]
- 470 Consent Needed
- The source of the request did not have the permission of the recipient to make such a request.[20]
- 480 Temporarily Unavailable
- Callee currently unavailable.[1]: §21.4.18
- 481 Call/Transaction Does Not Exist
- Server received a request that does not match any dialog or transaction.[1]: §21.4.19
- 482 Loop Detected
- Server has detected a loop.[1]: §21.4.20
- 483 Too Many Hops
- Max-Forwards header has reached the value ‘0’.[1]: §21.4.21
- 484 Address Incomplete
- Request-URI incomplete.[1]: §21.4.22
- 485 Ambiguous
- Request-URI is ambiguous.[1]: §21.4.23
- 486 Busy Here
- Callee is busy.[1]: §21.4.24
- 487 Request Terminated
- Request has terminated by bye or cancel.[1]: §21.4.25
- 488 Not Acceptable Here
- Some aspect of the session description or the Request-URI is not acceptable.[1]: §21.4.26
- 489 Bad Event
- The server did not understand an event package specified in an Event header field.[4]: §7.3.2 [6]: §8.3.2
- 491 Request Pending
- Server has some pending request from the same dialog.[1]: §21.4.27
- 493 Undecipherable
- Request contains an encrypted MIME body, which recipient can not decrypt.[1]: §21.4.28
- 494 Security Agreement Required
- The server has received a request that requires a negotiated security mechanism, and the response contains a list of suitable security mechanisms for the requester to choose between,[21]: §§2.3.1–2.3.2 or a digest authentication challenge.[21]: §2.4
5xx—Server Failure Responses[edit]
- 500 Internal Server Error
- The server could not fulfill the request due to some unexpected condition.[1]: §21.5.1
- 501 Not Implemented
- The server does not have the ability to fulfill the request, such as because it does not recognize the request method. (Compare with 405 Method Not Allowed, where the server recognizes the method but does not allow or support it.)[1]: §21.5.2
- 502 Bad Gateway
- The server is acting as a gateway or proxy, and received an invalid response from a downstream server while attempting to fulfill the request.[1]: §21.5.3
- 503 Service Unavailable
- The server is undergoing maintenance or is temporarily overloaded and so cannot process the request. A «Retry-After» header field may specify when the client may reattempt its request.[1]: §21.5.4
- 504 Server Time-out
- The server attempted to access another server in attempting to process the request, and did not receive a prompt response.[1]: §21.5.5
- 505 Version Not Supported
- The SIP protocol version in the request is not supported by the server.[1]: §21.5.6
- 513 Message Too Large
- The request message length is longer than the server can process.[1]: §21.5.7
- 555 Push Notification Service Not Supported
- The server does not support the push notification service identified in a ‘pn-provider’ SIP URI parameter[22]: §14.2.1
- 580 Precondition Failure
- The server is unable or unwilling to meet some constraints specified in the offer.[23]
6xx—Global Failure Responses[edit]
- 600 Busy Everywhere
- All possible destinations are busy. Unlike the 486 response, this response indicates the destination knows there are no alternative destinations (such as a voicemail server) able to accept the call.[1]: §21.6.1
- 603 Decline
- The destination does not wish to participate in the call, or cannot do so, and additionally the destination knows there are no alternative destinations (such as a voicemail server) willing to accept the call.[1]: §21.6.2 The response may indicate a better time to call in the Retry-After header field.
- 604 Does Not Exist Anywhere
- The server has authoritative information that the requested user does not exist anywhere.[1]: §21.6.3
- 606 Not Acceptable
- The user’s agent was contacted successfully but some aspects of the session description such as the requested media, bandwidth, or addressing style were not acceptable.[1]: §21.6.4
- 607 Unwanted
- The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected.[24]
- 608 Rejected
- An intermediary machine or process rejected the call attempt.[25] This contrasts with the 607 (Unwanted) SIP response code in which a human, the called party, rejected the call. The intermediary rejecting the call should include a Call-Info header with «purpose» value «jwscard», with the jCard[26] with contact details. The calling party can use this jCard if they want to dispute the rejection.
References[edit]
- ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az ba bb bc bd be bf bg bh bi bj bk bl Rosenberg, Jonathan; Schulzrinne, Henning; Camarillo, Gonzalo; Johnston, Alan; Peterson, Jon; Sparks, Robert; Handley, Mark; Schooler, Eve (June 2002). SIP: Session Initiation Protocol. IETF. doi:10.17487/RFC3261. RFC 3261.
- ^ a b c d Roach, Adam; Jennings, Cullen; Peterson, Jon; Barnes, Mary (17 April 2013) [Created January 2002]. «Response Codes». Session Initiation Protocol (SIP) Parameters. IANA.
- ^ Holmberg, Christer (May 2011). Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog. IETF. p. 1. Abstract. doi:10.17487/RFC6228. RFC 6228.
- ^ a b Roach, Adam B. (June 2002). Session Initiation Protocol (SIP)-Specific Event Notification. IETF. doi:10.17487/RFC3265. RFC 3265.
- ^ Fielding, Roy T.; Gettys, James; Mogul, Jeffrey C.; Nielsen, Henrik Frystyk; Masinter, Larry; Leach, Paul; Berners-Lee, Tim (June 1999). «202 Accepted». Hypertext Transfer Protocol — HTTP/1.1. IETF. sec. 10.2.3. doi:10.17487/RFC2616. RFC 2616.
- ^ a b Roach, Adam (July 2012). SIP-Specific Event Notification. IETF. doi:10.17487/RFC6665. RFC 6665.
- ^ Niemi, Aki (May 2010). «204 (No Notification) Response Code». In Willis, Dean (ed.). An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification. IETF. sec. 7.1. doi:10.17487/RFC5839. RFC 5839.
- ^ a b Handley, Mark; Schulzrinne, Henning; Schooler, Eve; Rosenberg, Jonathan (March 1999). SIP: Session Initiation Protocol. IETF. doi:10.17487/RFC2543. RFC 2543.
- ^ Niemi, Aki, ed. (2004). ««412 Conditional Requset Failed» Response Code». Session Initiation Protocol (SIP) Extension for Event State Publication. IETF. sec. 11.2.1. doi:10.17487/RFC3903. RFC 3903.
- ^ Schulzrinne, Henning; Polk, James (February 2006). «No Known Namespace or Priority Value». Communications Resource Priority for the Session Initiation Protocol (SIP). IETF. sec. 4.6.2. doi:10.17487/RFC4412. RFC 4412.
- ^ Donovan, Steve; Rosenberg, Jonathan (April 2005). «422 Response Code Definition». Session Timers in the Session Initiation Protocol (SIP). IETF. sec. 6. doi:10.17487/RFC4028. RFC 4028.
- ^ Polk, James; Rosen, Brian; Peterson, Jon (December 2011). «424 (Bad Location Information) Response Code». Location Conveyance for the Session Initiation Protocol. IETF. sec. 4.3. doi:10.17487/RFC6442. RFC 6442.
- ^ Rosen, Brian; Schulzrinne, Henning; Tschofenig, Hannes; Gellens, Randall (September 2020). «425 (Bad Alert Message) Response Code». Non-interactive Emergency Calls. IETF. sec. 5.1. doi:10.17487/RFC8876. RFC 8876.
- ^ a b c d Peterson, Jon; Jennings, Cullen (August 2006). Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC4474. RFC 4474.
- ^ Sparks, Robert J. (September 2004). «The 429 Provide Referrer Identity Error Response». The Session Initiation Protocol (SIP) Referred-By Mechanism. IETF. sec. 5. doi:10.17487/RFC3892. RFC 3892.
- ^ a b Jennings, Cullen; Mahy, Rohan; Audet, Francois, eds. (October 2009). Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC5626. RFC 5626.
- ^ Rosenberg, Jonathan (December 2007). «433 (Anonymity Disallowed) Definition». Rejecting Anonymous Requests in the Session Initiation Protocol (SIP). IETF. sec. 5. doi:10.17487/RFC5079. RFC 5079.
- ^ Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies. IETF. December 2008. doi:10.17487/RFC5393. RFC 5393.
- ^ Session Initiation Protocol (SIP) INFO Method and Package Framework. IETF. January 2011. doi:10.17487/RFC6086. RFC 6086.
- ^ Rosenberg, Jonathan; Willis, Dean (October 2008). «Definition of the 470 Response Code». In Camarillo, Gonzalo (ed.). A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP). IETF. sec. 5.9.2. doi:10.17487/RFC5360. RFC 5360.
- ^ a b Arkko, Jari; Torvinen, Vesa; Camarillo, Gonzalo; Niemi, Aki; Haukka, Tao (January 2003). Security Mechanism Agreement for the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC3329. RFC 3329.
- ^ Push Notification with the Session Initiation Protocol (SIP). IETF. May 2019. doi:10.17487/RFC8599. RFC 8599.
- ^ Rosenberg, Jonathan (October 2002). «Refusing an offer». In Camarillo, Gonzalo; Marshall, Bill (eds.). Integration of Resource Management and Session Initiation Protocol (SIP). IETF. sec. 8. doi:10.17487/RFC3312. RFC 3312.
- ^ A SIP Response Code for Unwanted Calls. IETF. July 2017. doi:10.17487/RFC8197. RFC 8197.
- ^ A Session Initiation Protocol (SIP) Response Code for Rejected Calls. IETF. December 2019. doi:10.17487/RFC8688. RFC 8688.
- ^ RFC 7095
External links[edit]
- Mapping SIP Error Messages to DSS1 codes at the Wayback Machine (archived 2021-04-12)
- Session Initiation Protocol (SIP) Parameters Contains a registry of different SIP parameters, including response codes
Very often problem is with incompatible codecs.
Example:
Capabilities: us - 0x0 (nothing), peer - audio=0x906 (gsm|ulaw|g726|g729)/video=0x0 (nothing), combined - 0x0 (nothing) Non-codec capabilities (dtmf): us - 0x1 (telephone-event), peer - 0x1 (telephone-event), combined - 0x1 (telephone-event)
<--- Reliably Transmitting (NAT) to 11.22.33.44:5060 ---> SIP/2.0 488 Not acceptable here
This line is important:
Capabilities: us - 0x0 (nothing), peer - audio=0x906 (gsm|ulaw|g726|g729)/video=0x0 (nothing), combined - 0x0 (nothing)
One end does not allow any codecs for this connection.
Enable some of these codecs: gsm|ulaw|g726|g729 and call should pass.
It can happen that Asterisk will return «488 Not acceptable here» if caller device asks for T38 support, but it is no enabled in Device settings.
Example of such invite:
<--- SIP read from UDP:1.1.1.1:5060 ---> INVITE sip:1234567890@2.2.2.2;user=phone SIP/2.0 Max-Forwards: 69 Session-Expires: 3600;refresher=uac Min-SE: 600 Supported: timer, 100rel To: <sip:1234567890@2.2.2.2:5060;user=phone> From: <sip:0987654321@1.1.1.1>;tag=3557129436-488864 P-Asserted-Identity: <sip:0987654321@1.1.1.1;user=phone> Call-ID: 30549129-3557129436-488859@abc.domain.com CSeq: 1 INVITE Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK5fe3cef54d2beba3e277c973dfde60d7 Contact: <sip:0987654321@1.1.1.1:5060> Call-Info: <sip:1.1.1.1>;method="NOTIFY;Event=telephone-event;Duration=1000" Content-Type: application/sdp Content-Length: 360 v=0 o=SBC2 839077453 839077453 IN IP4 1.1.1.1 s=sip call c=IN IP4 1.1.1.1 t=0 0 m=audio 52754 RTP/AVP 18 8 101 a=fmtp:18 annexb=no a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=image 52756 udptl t38 a=T38MaxBitRate:14400 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:1024 a=T38FaxMaxDatagram:238
In this case option «T.38 Support» should be enabled on Device settings to allow call go through.
Check also:
- SIP Error Codes
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:30.997268 [DEBUG] switch_core_state_machine.c:603 (sofia/internal/05@voip.domain.com) State NEW
2018-03-07 21:32:31.097307 [DEBUG] sofia.c:2442 Re-attaching to session ba678910-48af-4237-9464-c237e86b4ffa
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.117257 [DEBUG] sofia.c:9873 sofia/internal/05@voip.domain.com receiving invite from 166.177.123.5:62671 version: 1.6.20 -37-987c9b9 64bit
2018-03-07 21:32:31.117257 [DEBUG] sofia.c:10044 IP 166.177.123.5 Rejected by acl "domains". Falling back to Digest auth.
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] sofia.c:11168 Setting NAT mode based on via received
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] sofia.c:7084 Channel sofia/internal/05@voip.domain.com entering state [received][100]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] sofia.c:7094 Remote SDP:
ba678910-48af-4237-9464-c237e86b4ffa v=0
ba678910-48af-4237-9464-c237e86b4ffa o=05 8000 8000 IN IP4 10.80.136.201
ba678910-48af-4237-9464-c237e86b4ffa s=SIP Call
ba678910-48af-4237-9464-c237e86b4ffa c=IN IP4 10.80.136.201
ba678910-48af-4237-9464-c237e86b4ffa t=0 0
ba678910-48af-4237-9464-c237e86b4ffa m=audio 49744 RTP/AVP 0 8 9 123 2 97 3 18 101
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:0 PCMU/8000
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:8 PCMA/8000
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:9 G722/8000
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:123 opus/48000/2
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:2 G726-32/8000
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:97 iLBC/8000
ba678910-48af-4237-9464-c237e86b4ffa a=fmtp:97 mode=30
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:3 GSM/8000
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:18 G729/8000
ba678910-48af-4237-9464-c237e86b4ffa a=fmtp:18 annexb=no
ba678910-48af-4237-9464-c237e86b4ffa a=rtpmap:101 telephone-event/8000
ba678910-48af-4237-9464-c237e86b4ffa a=fmtp:101 0-15
ba678910-48af-4237-9464-c237e86b4ffa a=rtcp:49745 IN IP4 10.80.136.201
ba678910-48af-4237-9464-c237e86b4ffa a=ptime:20
ba678910-48af-4237-9464-c237e86b4ffa
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4504 Audio Codec Compare [PCMU:0:8000:20:64000:1] ++++ is saved as a match
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4504 Audio Codec Compare [PCMA:8:8000:20:64000:1] ++++ is saved as a match
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G722:9:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G722:9:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [opus:123:48000:20:0:2]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [opus:123:48000:20:0:2]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G726-32:2:8000:20:0:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G726-32:2:8000:20:0:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [iLBC:97:8000:20:0:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [iLBC:97:8000:20:0:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [GSM:3:8000:20:13200:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [GSM:3:8000:20:13200:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G729:18:8000:20:8000:1]/[PCMU:0:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4449 Audio Codec Compare [G729:18:8000:20:8000:1]/[PCMA:8:8000:20:64000:1]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4365 Set telephone-event payload to 101@8000
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:3061 Set Codec sofia/internal/05@voip.domain.com PCMU/8000 20 ms 160 samples 64000 bits 1 channels
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_codec.c:111 sofia/internal/05@voip.domain.com Original read codec set to PCMU:0
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4708 Set telephone-event payload to 101@8000
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_media.c:4767 sofia/internal/05@voip.domain.com Set 2833 dtmf send payload to 101 recv payload to 101
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] sofia.c:7507 (sofia/internal/05@voip.domain.com) State Change CS_NEW -> CS_INIT
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/05@voip.domain.com) Running State Change CS_INIT (Cur 1 Tot 5)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:627 (sofia/internal/05@voip.domain.com) State INIT
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] mod_sofia.c:90 sofia/internal/05@voip.domain.com SOFIA INIT
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:40 sofia/internal/05@voip.domain.com Standard INIT
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:48 (sofia/internal/05@voip.domain.com) State Change CS_INIT -> CS_ROUTING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:627 (sofia/internal/05@voip.domain.com) State INIT going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/05@voip.domain.com) Running State Change CS_ROUTING (Cur 1 Tot 5)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_channel.c:2249 (sofia/internal/05@voip.domain.com) Callstate Change DOWN -> RINGING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:643 (sofia/internal/05@voip.domain.com) State ROUTING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] mod_sofia.c:143 sofia/internal/05@voip.domain.com SOFIA ROUTING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [DEBUG] switch_core_state_machine.c:236 sofia/internal/05@voip.domain.com Standard ROUTING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.137497 [INFO] mod_dialplan_xml.c:637 Processing 05 <05>->5404963 in context voip.domain.com
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->user_exists] continue=true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_exists] () =~ // break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(user_exists=${user_exists id ${destination_number} ${domain_name}}) INLINE
2018-03-07 21:32:31.177231 [DEBUG] freeswitch_lua.cpp:365 DBH handle 0x7fa3ac126c90 Connected.
2018-03-07 21:32:31.177231 [DEBUG] freeswitch_lua.cpp:382 DBH handle 0x7fa3ac126c90 released.
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(user_exists=false)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.177231 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [user_exists]=[false]
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_exists] ${user_exists}(false) =~ /^true$/ break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->call-direction] continue=true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [call-direction] ${call_direction}() =~ /^(inbound|outbound|local)$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com ANTI-Action set(call_direction=local)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->variables] continue=true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [variables] () =~ // break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action export(origination_callee_id_name=${destination_number})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(RFC2822_DATE=${strftime(%a, %d %b %Y %T %z)})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->user_record] continue=true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] () =~ // break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(user_record=${user_data ${destination_number}@${domain_name} var user_record}) INLINE
2018-03-07 21:32:31.177231 [DEBUG] freeswitch_lua.cpp:365 DBH handle 0x7fa3ac126c90 Connected.
2018-03-07 21:32:31.177231 [DEBUG] freeswitch_lua.cpp:382 DBH handle 0x7fa3ac126c90 released.
2018-03-07 21:32:31.197229 [DEBUG] freeswitch_lua.cpp:365 DBH handle 0x7fa3ac126c90 Connected.
2018-03-07 21:32:31.197229 [DEBUG] freeswitch_lua.cpp:382 DBH handle 0x7fa3ac126c90 released.
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(user_record=)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [user_record]=[UNDEF]
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(from_user_exists=${user_exists id ${sip_from_user} ${sip_from_host}}) INLINE
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(from_user_exists=true)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [from_user_exists]=[true]
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_exists}(false) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_record}() =~ /^all$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_exists}(false) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^inbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_record}() =~ /^inbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_exists}(false) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^outbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_record}() =~ /^outbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_exists}(false) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^local$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${user_record}() =~ /^local$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] ${from_user_exists}(true) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(from_user_record=${user_data ${sip_from_user}@${sip_from_host} var user_record}) INLINE
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(from_user_record=)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [from_user_record]=[UNDEF]
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] ${from_user_exists}(true) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${from_user_record}() =~ /^all$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] ${from_user_exists}(true) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^inbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${from_user_record}() =~ /^inbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] ${from_user_exists}(true) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^outbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${from_user_record}() =~ /^outbound$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [user_record] ${from_user_exists}(true) =~ /^true$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${call_direction}() =~ /^local$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${from_user_record}() =~ /^local$/ break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [user_record] ${record_session}() =~ /^true$/ break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->redial] continue=true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [redial] destination_number(5404963) =~ /^(redial|*870)$/ break=on-true
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [redial] () =~ // break=never
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action hash(insert/${domain_name}-last_dial/${caller_id_number}/${destination_number})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->speed_dial] continue=false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [speed_dial] destination_number(5404963) =~ /^*0(.*)$/ break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->telnyx.1d10] continue=false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (FAIL) [telnyx.1d10] destination_number(5404963) =~ /^+?1?(d{10})$/ break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com parsing [voip.domain.com->telnyx.7d] continue=false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Regex (PASS) [telnyx.7d] destination_number(5404963) =~ /^(d{7})$/ break=on-false
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(sip_h_X-accountcode=${accountcode})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(call_direction=outbound)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action unset(call_timeout)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(hangup_after_bridge=true)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(effective_caller_id_name=${outbound_caller_id_name})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(effective_caller_id_number=${outbound_caller_id_number})
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(inherit_codec=true)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(ignore_display_updates=true)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(callee_id_number=5404963)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action set(continue_on_fail=true)
ba678910-48af-4237-9464-c237e86b4ffa Dialplan: sofia/internal/05@voip.domain.com Action bridge(sofia/gateway/e3d35ec4-3bf3-4343-b5db-f850372ab203/1xxx5404963)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_core_state_machine.c:286 (sofia/internal/05@voip.domain.com) State Change CS_ROUTING -> CS_EXECUTE
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_core_state_machine.c:643 (sofia/internal/05@voip.domain.com) State ROUTING going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/05@voip.domain.com) Running State Change CS_EXECUTE (Cur 1 Tot 5)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_core_state_machine.c:650 (sofia/internal/05@voip.domain.com) State EXECUTE
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_sofia.c:198 sofia/internal/05@voip.domain.com SOFIA EXECUTE
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_core_state_machine.c:328 sofia/internal/05@voip.domain.com Standard EXECUTE
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(call_direction=local)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [call_direction]=[local]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com export(origination_callee_id_name=5404963)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] switch_channel.c:1296 EXPORT (export_vars) [origination_callee_id_name]=[5404963]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(RFC2822_DATE=Wed, 07 Mar 2018 21:32:31 +0000)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [RFC2822_DATE]=[Wed, 07 Mar 2018 21:32:31 +0000]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com hash(insert/voip.domain.com-last_dial/05/5404963)
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(sip_h_X-accountcode=voip.domain.com)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [sip_h_X-accountcode]=[voip.domain.com]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(call_direction=outbound)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [call_direction]=[outbound]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com unset(call_timeout)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1693 UNSET [call_timeout]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(hangup_after_bridge=true)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [hangup_after_bridge]=[true]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(effective_caller_id_name=Bryan)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.197229 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [effective_caller_id_name]=[Bryan]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(effective_caller_id_number=8706926477)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [effective_caller_id_number]=[8706926477]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(inherit_codec=true)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [inherit_codec]=[true]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(ignore_display_updates=true)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [ignore_display_updates]=[true]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(callee_id_number=5404963)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [callee_id_number]=[5404963]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com set(continue_on_fail=true)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] mod_dptools.c:1548 SET sofia/internal/05@voip.domain.com [continue_on_fail]=[true]
ba678910-48af-4237-9464-c237e86b4ffa EXECUTE sofia/internal/05@voip.domain.com bridge(sofia/gateway/e3d35ec4-3bf3-4343-b5db-f850372ab203/1xxx5404963)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] switch_channel.c:1250 sofia/internal/05@voip.domain.com EXPORTING[export_vars] [domain_name]=[voip.domain.com] to event
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] switch_channel.c:1250 sofia/internal/05@voip.domain.com EXPORTING[export_vars] [origination_callee_id_name]=[5404963] to event
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.217232 [DEBUG] switch_ivr_originate.c:2142 Parsing global variables
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [NOTICE] switch_channel.c:1104 New Channel sofia/external/1xxx5404963 [0a2e05f3-2cd2-4109-a826-319fc0f86fed]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] mod_sofia.c:4819 (sofia/external/1xxx5404963) State Change CS_NEW -> CS_INIT
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:584 (sofia/external/1xxx5404963) Running State Change CS_INIT (Cur 2 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:627 (sofia/external/1xxx5404963) State INIT
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] mod_sofia.c:90 sofia/external/1xxx5404963 SOFIA INIT
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] sofia_glue.c:1295 sofia/external/1xxx5404963 sending invite version: 1.6.20 -37-987c9b9 64bit
0a2e05f3-2cd2-4109-a826-319fc0f86fed Local SDP:
0a2e05f3-2cd2-4109-a826-319fc0f86fed v=0
0a2e05f3-2cd2-4109-a826-319fc0f86fed o=FreeSWITCH 1520436009 1520436010 IN IP4 <server ip address>
0a2e05f3-2cd2-4109-a826-319fc0f86fed s=FreeSWITCH
0a2e05f3-2cd2-4109-a826-319fc0f86fed c=IN IP4 <server ip address>
0a2e05f3-2cd2-4109-a826-319fc0f86fed t=0 0
0a2e05f3-2cd2-4109-a826-319fc0f86fed m=audio 22342 RTP/AVP 0 8 101 13
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=rtpmap:0 PCMU/8000
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=rtpmap:8 PCMA/8000
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=rtpmap:101 telephone-event/8000
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=fmtp:101 0-16
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=rtpmap:13 CN/8000
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=ptime:20
0a2e05f3-2cd2-4109-a826-319fc0f86fed a=sendrecv
0a2e05f3-2cd2-4109-a826-319fc0f86fed
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:40 sofia/external/1xxx5404963 Standard INIT
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:48 (sofia/external/1xxx5404963) State Change CS_INIT -> CS_ROUTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:627 (sofia/external/1xxx5404963) State INIT going to sleep
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:584 (sofia/external/1xxx5404963) Running State Change CS_ROUTING (Cur 2 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] sofia.c:7084 Channel sofia/external/1xxx5404963 entering state [calling][0]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:643 (sofia/external/1xxx5404963) State ROUTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] mod_sofia.c:143 sofia/external/1xxx5404963 SOFIA ROUTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_ivr_originate.c:67 (sofia/external/1xxx5404963) State Change CS_ROUTING -> CS_CONSUME_MEDIA
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:643 (sofia/external/1xxx5404963) State ROUTING going to sleep
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:584 (sofia/external/1xxx5404963) Running State Change CS_CONSUME_MEDIA (Cur 2 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:662 (sofia/external/1xxx5404963) State CONSUME_MEDIA
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.217232 [DEBUG] switch_core_state_machine.c:662 (sofia/external/1xxx5404963) State CONSUME_MEDIA going to sleep
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.277265 [DEBUG] sofia.c:7084 Channel sofia/external/1xxx5404963 entering state [calling][0]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.377265 [DEBUG] sofia.c:7084 Channel sofia/external/1xxx5404963 entering state [proceeding][180]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.377265 [NOTICE] sofia.c:7192 Ring-Ready sofia/external/1xxx5404963!
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:31.377265 [DEBUG] switch_channel.c:3346 (sofia/external/1xxx5404963) Callstate Change DOWN -> RINGING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.397265 [NOTICE] mod_sofia.c:2273 Ring-Ready sofia/internal/05@voip.domain.com!
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.397265 [DEBUG] sofia.c:7084 Channel sofia/internal/05@voip.domain.com entering state [early][180]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:31.397265 [NOTICE] switch_ivr_originate.c:525 Ring Ready sofia/internal/05@voip.domain.com!
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] sofia.c:6257 Remote Reason: 88
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] sofia.c:7084 Channel sofia/external/1xxx5404963 entering state [terminated][488]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [NOTICE] sofia.c:8273 Hangup sofia/external/1xxx5404963 [CS_CONSUME_MEDIA] [INCOMPATIBLE_DESTINATION]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:584 (sofia/external/1xxx5404963) Running State Change CS_HANGUP (Cur 2 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:850 (sofia/external/1xxx5404963) Callstate Change RINGING -> HANGUP
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:852 (sofia/external/1xxx5404963) State HANGUP
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] mod_sofia.c:438 Channel sofia/external/1xxx5404963 hanging up, cause: INCOMPATIBLE_DESTINATION
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:60 sofia/external/1xxx5404963 Standard HANGUP, cause: INCOMPATIBLE_DESTINATION
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:852 (sofia/external/1xxx5404963) State HANGUP going to sleep
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:619 (sofia/external/1xxx5404963) State Change CS_HANGUP -> CS_REPORTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:584 (sofia/external/1xxx5404963) Running State Change CS_REPORTING (Cur 2 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:938 (sofia/external/1xxx5404963) State REPORTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:174 sofia/external/1xxx5404963 Standard REPORTING, cause: INCOMPATIBLE_DESTINATION
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:938 (sofia/external/1xxx5404963) State REPORTING going to sleep
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:610 (sofia/external/1xxx5404963) State Change CS_REPORTING -> CS_DESTROY
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_session.c:1665 Session 6 (sofia/external/1xxx5404963) Locked, Waiting on external entities
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_ivr_originate.c:3848 Originate Resulted in Error Cause: 88 [INCOMPATIBLE_DESTINATION]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [INFO] mod_dptools.c:3436 Originate Failed. Cause: INCOMPATIBLE_DESTINATION
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [NOTICE] switch_core_state_machine.c:385 sofia/internal/05@voip.domain.com has executed the last dialplan instruction, hanging up.
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [NOTICE] switch_core_state_machine.c:387 Hangup sofia/internal/05@voip.domain.com [CS_EXECUTE] [NORMAL_CLEARING]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:650 (sofia/internal/05@voip.domain.com) State EXECUTE going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/05@voip.domain.com) Running State Change CS_HANGUP (Cur 2 Tot 6)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/05@voip.domain.com) Callstate Change RINGING -> HANGUP
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:852 (sofia/internal/05@voip.domain.com) State HANGUP
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] mod_sofia.c:432 sofia/internal/05@voip.domain.com Overriding SIP cause 480 with 488 from the other leg
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] mod_sofia.c:438 Channel sofia/internal/05@voip.domain.com hanging up, cause: NORMAL_CLEARING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] mod_sofia.c:577 Responding to INVITE with: 488
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:60 sofia/internal/05@voip.domain.com Standard HANGUP, cause: NORMAL_CLEARING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:852 (sofia/internal/05@voip.domain.com) State HANGUP going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:619 (sofia/internal/05@voip.domain.com) State Change CS_HANGUP -> CS_REPORTING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/05@voip.domain.com) Running State Change CS_REPORTING (Cur 2 Tot 6)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/05@voip.domain.com) State REPORTING
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [NOTICE] switch_core_session.c:1683 Session 6 (sofia/external/1xxx5404963) Ended
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [NOTICE] switch_core_session.c:1687 Close Channel sofia/external/1xxx5404963 [CS_DESTROY]
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:741 (sofia/external/1xxx5404963) Running State Change CS_DESTROY (Cur 1 Tot 6)
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:751 (sofia/external/1xxx5404963) State DESTROY
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] mod_sofia.c:343 sofia/external/1xxx5404963 SOFIA DESTROY
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:181 sofia/external/1xxx5404963 Standard DESTROY
0a2e05f3-2cd2-4109-a826-319fc0f86fed 2018-03-07 21:32:34.237252 [DEBUG] switch_core_state_machine.c:751 (sofia/external/1xxx5404963) State DESTROY going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:174 sofia/internal/05@voip.domain.com Standard REPORTING, cause: NORMAL_CLEARING
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/05@voip.domain.com) State REPORTING going to sleep
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:610 (sofia/internal/05@voip.domain.com) State Change CS_REPORTING -> CS_DESTROY
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_session.c:1665 Session 5 (sofia/internal/05@voip.domain.com) Locked, Waiting on external entities
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [NOTICE] switch_core_session.c:1683 Session 5 (sofia/internal/05@voip.domain.com) Ended
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [NOTICE] switch_core_session.c:1687 Close Channel sofia/internal/05@voip.domain.com [CS_DESTROY]
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:741 (sofia/internal/05@voip.domain.com) Running State Change CS_DESTROY (Cur 0 Tot 6)
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/05@voip.domain.com) State DESTROY
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] mod_sofia.c:343 sofia/internal/05@voip.domain.com SOFIA DESTROY
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:181 sofia/internal/05@voip.domain.com Standard DESTROY
ba678910-48af-4237-9464-c237e86b4ffa 2018-03-07 21:32:34.277241 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/05@voip.domain.com) State DESTROY going to sleep
2018-03-07 21:34:27.497236 [DEBUG] switch_rtp.c:1463 [ zrtp cache]: Storing ZRTP cache to </var/lib/freeswitch/db/zrtp.dat>...
2018-03-07 21:34:27.497236 [DEBUG] switch_rtp.c:1324 Saving ZRTP cache: OK
2018-03-07 21:49:27.337400 [DEBUG] switch_rtp.c:1463 [ zrtp cache]: Storing ZRTP cache to </var/lib/freeswitch/db/zrtp.dat>...
2018-03-07 21:49:27.337400 [DEBUG] switch_rtp.c:1324 Saving ZRTP cache: OK
2018-03-07 22:04:27.157249 [DEBUG] switch_rtp.c:1463 [ zrtp cache]: Storing ZRTP cache to </var/lib/freeswitch/db/zrtp.dat>...
2018-03-07 22:04:27.157249 [DEBUG] switch_rtp.c:1324 Saving ZRTP cache: OK
