提交 27a5a679 authored 作者: Michael Jerris's avatar Michael Jerris

Thu Jan 15 09:38:34 CST 2009 Bernhard Suttner <bernhard DOT suttner AT comdasys DOT com>

  * sip_util.c: fix 484 respose to REFER in sip_response_terminates_dialog()

  Asterisk (v 1.2.7.1) does response with 484 if a client does send a refer
  with a @ReferTo header to an unknown number.  This is therefore not
  fundamentally wrong and the dialog should not be destroyed!



git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@11829 d0543943-73ff-0310-b7d9-9358b9ac24b2
上级 48b5844e
Wed Feb 11 11:00:10 CST 2009 Wed Feb 11 11:03:24 CST 2009
...@@ -1164,14 +1164,25 @@ int sip_response_terminates_dialog(int response_code, ...@@ -1164,14 +1164,25 @@ int sip_response_terminates_dialog(int response_code,
return 0; return 0;
case 484: /* Address Incomplete */ case 484: /* Address Incomplete */
case 485: /* Ambiguous */
/** @par 484 Address Incomplete and 485 Ambiguous /** @par 484 Address Incomplete and 485 Ambiguous
Similar to 404 and 410, these Similar to 404 and 410, these
responses came to a request whose Request-URI was provided by the responses came to a request whose Request-URI was provided by the
peer in a @Contact header field. Something has gone fundamentally peer in a @Contact header field. Something has gone fundamentally
wrong, and the dialog and all of its usages are destroyed. wrong, and the dialog and all of its usages are destroyed.
Asterisk (v 1.2.7.1) does response with 484 if a client does send a refer
with a @ReferTo header to an unknown number. This is therefore not
fundamentally wrong and the dialog should not be destroyed!
*/ */
if (method == sip_method_refer)
{
*return_graceful_terminate_usage = 0;
return 0;
}
case 485: /* Ambiguous */
return terminate_dialog; return terminate_dialog;
case 486: /** @par 486 Busy Here case 486: /** @par 486 Busy Here
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论