|
|
|
|
@ -67,6 +67,7 @@ Juha Heinanen
|
|
|
|
|
4.43. remap_503_500 (boolean)
|
|
|
|
|
4.44. failure_exec_mode (boolean)
|
|
|
|
|
4.45. dns_reuse_rcv_socket (boolean)
|
|
|
|
|
4.46. xavp_contact (string)
|
|
|
|
|
|
|
|
|
|
5. Functions
|
|
|
|
|
|
|
|
|
|
@ -189,51 +190,52 @@ Juha Heinanen
|
|
|
|
|
1.43. Set remap_503_500 parameter
|
|
|
|
|
1.44. Set failure_exec_mode parameter
|
|
|
|
|
1.45. Set dns_reuse_rcv_socket parameter
|
|
|
|
|
1.46. t_relay usage
|
|
|
|
|
1.47. t_relay_to_udp usage
|
|
|
|
|
1.48. t_on_failure usage
|
|
|
|
|
1.49. t_on_branch_failure usage
|
|
|
|
|
1.50. t_on_reply usage
|
|
|
|
|
1.51. t_on_branch usage
|
|
|
|
|
1.52. t_newtran usage
|
|
|
|
|
1.53. t_reply usage
|
|
|
|
|
1.54. t_lookup_request usage
|
|
|
|
|
1.55. t_retransmit_reply usage
|
|
|
|
|
1.56. t_release usage
|
|
|
|
|
1.57. t_forward_nonack usage
|
|
|
|
|
1.58. t_set_fr usage
|
|
|
|
|
1.59. t_reset_fr usage
|
|
|
|
|
1.60. t_set_max_lifetime usage
|
|
|
|
|
1.61. t_reset_max_lifetime usage
|
|
|
|
|
1.62. t_set_retr usage
|
|
|
|
|
1.63. t_reset_retr usage
|
|
|
|
|
1.64. t_set_auto_inv_100 usage
|
|
|
|
|
1.65. t_branch_timeout usage
|
|
|
|
|
1.66. t_branch_replied usage
|
|
|
|
|
1.67. t_any_timeout usage
|
|
|
|
|
1.68. t_any_replied usage
|
|
|
|
|
1.69. t_grep_status usage
|
|
|
|
|
1.70. t_is_canceled usage
|
|
|
|
|
1.71. t_is_expired usage
|
|
|
|
|
1.72. t_relay_cancel usage
|
|
|
|
|
1.73. t_lookup_cancel usage
|
|
|
|
|
1.74. t_drop_replies() usage
|
|
|
|
|
1.75. t_save_lumps() usage
|
|
|
|
|
1.76. t_load_contacts usage
|
|
|
|
|
1.77. t_next_contacts usage
|
|
|
|
|
1.78. t_next_contact_flow usage
|
|
|
|
|
1.79. t_check_status usage
|
|
|
|
|
1.80. t_check_trans usage
|
|
|
|
|
1.81. t_set_disable_6xx usage
|
|
|
|
|
1.82. t_set_disable_failover usage
|
|
|
|
|
1.83. t_set_disable_internal_reply usage
|
|
|
|
|
1.84. t_replicate usage
|
|
|
|
|
1.85. t_relay_to usage
|
|
|
|
|
1.86. t_set_no_e2e_cancel_reason usage
|
|
|
|
|
1.87. t_replicate usage
|
|
|
|
|
1.88. t_use_uac_headers usage
|
|
|
|
|
1.89. t_is_retr_async_reply usage
|
|
|
|
|
1.90. event_route[tm:branch-failure] usage
|
|
|
|
|
1.46. Set xavp_contact parameter
|
|
|
|
|
1.47. t_relay usage
|
|
|
|
|
1.48. t_relay_to_udp usage
|
|
|
|
|
1.49. t_on_failure usage
|
|
|
|
|
1.50. t_on_branch_failure usage
|
|
|
|
|
1.51. t_on_reply usage
|
|
|
|
|
1.52. t_on_branch usage
|
|
|
|
|
1.53. t_newtran usage
|
|
|
|
|
1.54. t_reply usage
|
|
|
|
|
1.55. t_lookup_request usage
|
|
|
|
|
1.56. t_retransmit_reply usage
|
|
|
|
|
1.57. t_release usage
|
|
|
|
|
1.58. t_forward_nonack usage
|
|
|
|
|
1.59. t_set_fr usage
|
|
|
|
|
1.60. t_reset_fr usage
|
|
|
|
|
1.61. t_set_max_lifetime usage
|
|
|
|
|
1.62. t_reset_max_lifetime usage
|
|
|
|
|
1.63. t_set_retr usage
|
|
|
|
|
1.64. t_reset_retr usage
|
|
|
|
|
1.65. t_set_auto_inv_100 usage
|
|
|
|
|
1.66. t_branch_timeout usage
|
|
|
|
|
1.67. t_branch_replied usage
|
|
|
|
|
1.68. t_any_timeout usage
|
|
|
|
|
1.69. t_any_replied usage
|
|
|
|
|
1.70. t_grep_status usage
|
|
|
|
|
1.71. t_is_canceled usage
|
|
|
|
|
1.72. t_is_expired usage
|
|
|
|
|
1.73. t_relay_cancel usage
|
|
|
|
|
1.74. t_lookup_cancel usage
|
|
|
|
|
1.75. t_drop_replies() usage
|
|
|
|
|
1.76. t_save_lumps() usage
|
|
|
|
|
1.77. t_load_contacts usage
|
|
|
|
|
1.78. t_next_contacts usage
|
|
|
|
|
1.79. t_next_contact_flow usage
|
|
|
|
|
1.80. t_check_status usage
|
|
|
|
|
1.81. t_check_trans usage
|
|
|
|
|
1.82. t_set_disable_6xx usage
|
|
|
|
|
1.83. t_set_disable_failover usage
|
|
|
|
|
1.84. t_set_disable_internal_reply usage
|
|
|
|
|
1.85. t_replicate usage
|
|
|
|
|
1.86. t_relay_to usage
|
|
|
|
|
1.87. t_set_no_e2e_cancel_reason usage
|
|
|
|
|
1.88. t_replicate usage
|
|
|
|
|
1.89. t_use_uac_headers usage
|
|
|
|
|
1.90. t_is_retr_async_reply usage
|
|
|
|
|
1.91. event_route[tm:branch-failure] usage
|
|
|
|
|
|
|
|
|
|
Chapter 1. Admin Guide
|
|
|
|
|
|
|
|
|
|
@ -289,6 +291,7 @@ Chapter 1. Admin Guide
|
|
|
|
|
4.43. remap_503_500 (boolean)
|
|
|
|
|
4.44. failure_exec_mode (boolean)
|
|
|
|
|
4.45. dns_reuse_rcv_socket (boolean)
|
|
|
|
|
4.46. xavp_contact (string)
|
|
|
|
|
|
|
|
|
|
5. Functions
|
|
|
|
|
|
|
|
|
|
@ -655,6 +658,7 @@ failure_route["serial"]
|
|
|
|
|
4.43. remap_503_500 (boolean)
|
|
|
|
|
4.44. failure_exec_mode (boolean)
|
|
|
|
|
4.45. dns_reuse_rcv_socket (boolean)
|
|
|
|
|
4.46. xavp_contact (string)
|
|
|
|
|
|
|
|
|
|
4.1. fr_timer (integer)
|
|
|
|
|
|
|
|
|
|
@ -1564,6 +1568,18 @@ modparam("tm", "failure_exec_mode", 1)
|
|
|
|
|
modparam("tm", "dns_reuse_rcv_socket", 1)
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
4.46. xavp_contact (string)
|
|
|
|
|
|
|
|
|
|
The name of XAVP storing the attributes per contact. This must be the
|
|
|
|
|
same as the usrloc parameter xavp_contacts.
|
|
|
|
|
|
|
|
|
|
Default value is "NULL".
|
|
|
|
|
|
|
|
|
|
Example 1.46. Set xavp_contact parameter
|
|
|
|
|
...
|
|
|
|
|
modparam("tm|usrloc", "xavp_contact", "ulattrs")
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
5. Functions
|
|
|
|
|
|
|
|
|
|
5.1. t_relay([host, port])
|
|
|
|
|
@ -1637,7 +1653,7 @@ modparam("tm", "dns_reuse_rcv_socket", 1)
|
|
|
|
|
Returns a negative value on failure -- you may still want to send a
|
|
|
|
|
negative reply upstream statelessly not to leave upstream UAC in lurch.
|
|
|
|
|
|
|
|
|
|
Example 1.46. t_relay usage
|
|
|
|
|
Example 1.47. t_relay usage
|
|
|
|
|
...
|
|
|
|
|
if (!t_relay())
|
|
|
|
|
{
|
|
|
|
|
@ -1664,7 +1680,7 @@ if (!t_relay())
|
|
|
|
|
derived from the message uri (using sip sepcific DNS lookups), but with
|
|
|
|
|
the protocol corresponding to the function name.
|
|
|
|
|
|
|
|
|
|
Example 1.47. t_relay_to_udp usage
|
|
|
|
|
Example 1.48. t_relay_to_udp usage
|
|
|
|
|
...
|
|
|
|
|
if (src_ip==10.0.0.0/8)
|
|
|
|
|
t_relay_to_udp("1.2.3.4", "5060"); # sent to 1.2.3.4:5060 over udp
|
|
|
|
|
@ -1704,7 +1720,7 @@ else
|
|
|
|
|
Meaning of the parameters is as follows:
|
|
|
|
|
* failure_route - Failure route block to be called.
|
|
|
|
|
|
|
|
|
|
Example 1.48. t_on_failure usage
|
|
|
|
|
Example 1.49. t_on_failure usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_on_failure("1");
|
|
|
|
|
@ -1740,7 +1756,7 @@ failure_route[1] {
|
|
|
|
|
* branch_failure_route - Name of the branch_failure route block to be
|
|
|
|
|
called (it is prefixed internally with 'tm:branch-failure:').
|
|
|
|
|
|
|
|
|
|
Example 1.49. t_on_branch_failure usage
|
|
|
|
|
Example 1.50. t_on_branch_failure usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_on_branch_failure("myroute");
|
|
|
|
|
@ -1763,7 +1779,7 @@ event_route[tm:branch-failure:myroute] {
|
|
|
|
|
Meaning of the parameters is as follows:
|
|
|
|
|
* onreply_route - Onreply route block to be called.
|
|
|
|
|
|
|
|
|
|
Example 1.50. t_on_reply usage
|
|
|
|
|
Example 1.51. t_on_reply usage
|
|
|
|
|
...
|
|
|
|
|
loadmodule "/usr/local/lib/ser/modules/nathelper.so"
|
|
|
|
|
...
|
|
|
|
|
@ -1795,7 +1811,7 @@ es');
|
|
|
|
|
Meaning of the parameters is as follows:
|
|
|
|
|
* branch_route - branch route block to be called.
|
|
|
|
|
|
|
|
|
|
Example 1.51. t_on_branch usage
|
|
|
|
|
Example 1.52. t_on_branch usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_on_branch("1");
|
|
|
|
|
@ -1814,7 +1830,7 @@ branch_route[1] {
|
|
|
|
|
the only way a script can add a new transaction in an atomic way.
|
|
|
|
|
Typically, it is used to deploy a UAS.
|
|
|
|
|
|
|
|
|
|
Example 1.52. t_newtran usage
|
|
|
|
|
Example 1.53. t_newtran usage
|
|
|
|
|
...
|
|
|
|
|
if (t_newtran()) {
|
|
|
|
|
log("UAS logic");
|
|
|
|
|
@ -1844,7 +1860,7 @@ if (t_newtran()) {
|
|
|
|
|
* code - Reply code number.
|
|
|
|
|
* reason_phrase - Reason string.
|
|
|
|
|
|
|
|
|
|
Example 1.53. t_reply usage
|
|
|
|
|
Example 1.54. t_reply usage
|
|
|
|
|
...
|
|
|
|
|
t_reply("404", "Not found");
|
|
|
|
|
...
|
|
|
|
|
@ -1857,7 +1873,7 @@ t_reply("404", "Not found");
|
|
|
|
|
none was found. However this is safely (atomically) done using
|
|
|
|
|
t_newtran.
|
|
|
|
|
|
|
|
|
|
Example 1.54. t_lookup_request usage
|
|
|
|
|
Example 1.55. t_lookup_request usage
|
|
|
|
|
...
|
|
|
|
|
if (t_lookup_request()) {
|
|
|
|
|
...
|
|
|
|
|
@ -1868,7 +1884,7 @@ if (t_lookup_request()) {
|
|
|
|
|
|
|
|
|
|
Retransmits a reply sent previously by UAS transaction.
|
|
|
|
|
|
|
|
|
|
Example 1.55. t_retransmit_reply usage
|
|
|
|
|
Example 1.56. t_retransmit_reply usage
|
|
|
|
|
...
|
|
|
|
|
t_retransmit_reply();
|
|
|
|
|
...
|
|
|
|
|
@ -1878,7 +1894,7 @@ t_retransmit_reply();
|
|
|
|
|
Remove transaction from memory (it will be first put on a wait timer to
|
|
|
|
|
absorb delayed messages).
|
|
|
|
|
|
|
|
|
|
Example 1.56. t_release usage
|
|
|
|
|
Example 1.57. t_release usage
|
|
|
|
|
...
|
|
|
|
|
t_release();
|
|
|
|
|
...
|
|
|
|
|
@ -1892,7 +1908,7 @@ t_release();
|
|
|
|
|
* ip - IP address where the message should be sent.
|
|
|
|
|
* port - Port number.
|
|
|
|
|
|
|
|
|
|
Example 1.57. t_forward_nonack usage
|
|
|
|
|
Example 1.58. t_forward_nonack usage
|
|
|
|
|
...
|
|
|
|
|
t_forward_nonack("1.2.3.4", "5060");
|
|
|
|
|
...
|
|
|
|
|
@ -1931,7 +1947,7 @@ t_forward_nonack("1.2.3.4", "5060");
|
|
|
|
|
|
|
|
|
|
See also: fr_timer, fr_inv_timer, t_reset_fr().
|
|
|
|
|
|
|
|
|
|
Example 1.58. t_set_fr usage
|
|
|
|
|
Example 1.59. t_set_fr usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_set_fr(10000); # set only fr invite timeout to 10s
|
|
|
|
|
@ -1958,7 +1974,7 @@ branch_route[1] {
|
|
|
|
|
|
|
|
|
|
See also: fr_timer, fr_inv_timer, t_set_fr.
|
|
|
|
|
|
|
|
|
|
Example 1.59. t_reset_fr usage
|
|
|
|
|
Example 1.60. t_reset_fr usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -1984,7 +2000,7 @@ route {
|
|
|
|
|
|
|
|
|
|
See also: max_inv_lifetime, max_noninv_lifetime, t_reset_max_lifetime.
|
|
|
|
|
|
|
|
|
|
Example 1.60. t_set_max_lifetime usage
|
|
|
|
|
Example 1.61. t_set_max_lifetime usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
if (src_ip=1.2.3.4)
|
|
|
|
|
@ -2006,7 +2022,7 @@ route {
|
|
|
|
|
|
|
|
|
|
See also: max_inv_lifetime, max_noninv_lifetime, t_set_max_lifetime.
|
|
|
|
|
|
|
|
|
|
Example 1.61. t_reset_max_lifetime usage
|
|
|
|
|
Example 1.62. t_reset_max_lifetime usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2044,7 +2060,7 @@ route {
|
|
|
|
|
|
|
|
|
|
See also: retr_timer1, retr_timer2, t_reset_retr().
|
|
|
|
|
|
|
|
|
|
Example 1.62. t_set_retr usage
|
|
|
|
|
Example 1.63. t_set_retr usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_set_retr(250, 0); # set only T1 to 250 ms
|
|
|
|
|
@ -2071,7 +2087,7 @@ branch_route[1] {
|
|
|
|
|
|
|
|
|
|
See also: retr_timer1, retr_timer2, t_set_retr.
|
|
|
|
|
|
|
|
|
|
Example 1.63. t_reset_retr usage
|
|
|
|
|
Example 1.64. t_reset_retr usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2087,7 +2103,7 @@ route {
|
|
|
|
|
|
|
|
|
|
See also: auto_inv_100.
|
|
|
|
|
|
|
|
|
|
Example 1.64. t_set_auto_inv_100 usage
|
|
|
|
|
Example 1.65. t_set_auto_inv_100 usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2102,7 +2118,7 @@ route {
|
|
|
|
|
timeout. It can be used from failure_route and branch-failure event
|
|
|
|
|
route.
|
|
|
|
|
|
|
|
|
|
Example 1.65. t_branch_timeout usage
|
|
|
|
|
Example 1.66. t_branch_timeout usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (t_branch_timeout()){
|
|
|
|
|
@ -2118,7 +2134,7 @@ failure_route[0]{
|
|
|
|
|
taken into account). It can be used from failure_route and
|
|
|
|
|
branch-failure event route.
|
|
|
|
|
|
|
|
|
|
Example 1.66. t_branch_replied usage
|
|
|
|
|
Example 1.67. t_branch_replied usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (t_branch_timeout()){
|
|
|
|
|
@ -2135,7 +2151,7 @@ failure_route[0]{
|
|
|
|
|
Returns true if at least one of the current transactions branches did
|
|
|
|
|
timeout.
|
|
|
|
|
|
|
|
|
|
Example 1.67. t_any_timeout usage
|
|
|
|
|
Example 1.68. t_any_timeout usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (!t_branch_timeout()){
|
|
|
|
|
@ -2152,7 +2168,7 @@ failure_route[0]{
|
|
|
|
|
receive some reply in the past. If called from a failure or onreply
|
|
|
|
|
route, the "current" reply is not taken into account.
|
|
|
|
|
|
|
|
|
|
Example 1.68. t_any_replied usage
|
|
|
|
|
Example 1.69. t_any_replied usage
|
|
|
|
|
...
|
|
|
|
|
onreply_route[0]{
|
|
|
|
|
if (!t_any_replied()){
|
|
|
|
|
@ -2166,7 +2182,7 @@ onreply_route[0]{
|
|
|
|
|
Returns true if "code" is the final reply received (or locally
|
|
|
|
|
generated) in at least one of the current transactions branches.
|
|
|
|
|
|
|
|
|
|
Example 1.69. t_grep_status usage
|
|
|
|
|
Example 1.70. t_grep_status usage
|
|
|
|
|
...
|
|
|
|
|
onreply_route[0]{
|
|
|
|
|
if (t_grep_status("486")){
|
|
|
|
|
@ -2179,7 +2195,7 @@ onreply_route[0]{
|
|
|
|
|
|
|
|
|
|
Returns true if the current transaction was canceled.
|
|
|
|
|
|
|
|
|
|
Example 1.70. t_is_canceled usage
|
|
|
|
|
Example 1.71. t_is_canceled usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (t_is_canceled()){
|
|
|
|
|
@ -2193,7 +2209,7 @@ failure_route[0]{
|
|
|
|
|
Returns true if the current transaction has already been expired, i.e.
|
|
|
|
|
the max_inv_lifetime/max_noninv_lifetime interval has already elapsed.
|
|
|
|
|
|
|
|
|
|
Example 1.71. t_is_expired usage
|
|
|
|
|
Example 1.72. t_is_expired usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (t_is_expired()){
|
|
|
|
|
@ -2214,7 +2230,7 @@ failure_route[0]{
|
|
|
|
|
CANCELs were successfully sent to the pending branches, true if the
|
|
|
|
|
INVITE was not found, and false in case of any error.
|
|
|
|
|
|
|
|
|
|
Example 1.72. t_relay_cancel usage
|
|
|
|
|
Example 1.73. t_relay_cancel usage
|
|
|
|
|
if (method == CANCEL) {
|
|
|
|
|
if (!t_relay_cancel()) { # implicit drop if relaying was successful,
|
|
|
|
|
# nothing to do
|
|
|
|
|
@ -2241,7 +2257,7 @@ if (method == CANCEL) {
|
|
|
|
|
overwritten with the flags of the INVITE. isflagset() can be used to
|
|
|
|
|
check the flags of the previously forwarded INVITE in this case.
|
|
|
|
|
|
|
|
|
|
Example 1.73. t_lookup_cancel usage
|
|
|
|
|
Example 1.74. t_lookup_cancel usage
|
|
|
|
|
if (method == CANCEL) {
|
|
|
|
|
if (t_lookup_cancel()) {
|
|
|
|
|
log("INVITE transaction exists");
|
|
|
|
|
@ -2271,7 +2287,7 @@ if (method == CANCEL) {
|
|
|
|
|
Dropping replies works only if a new branch is added to the
|
|
|
|
|
transaction, or it is explicitly replied in the script!
|
|
|
|
|
|
|
|
|
|
Example 1.74. t_drop_replies() usage
|
|
|
|
|
Example 1.75. t_drop_replies() usage
|
|
|
|
|
...
|
|
|
|
|
failure_route[0]{
|
|
|
|
|
if (t_check_status("5[0-9][0-9]")){
|
|
|
|
|
@ -2302,7 +2318,7 @@ failure_route[0]{
|
|
|
|
|
The transaction must be created by t_newtran() before calling
|
|
|
|
|
t_save_lumps().
|
|
|
|
|
|
|
|
|
|
Example 1.75. t_save_lumps() usage
|
|
|
|
|
Example 1.76. t_save_lumps() usage
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
t_newtran();
|
|
|
|
|
@ -2361,7 +2377,7 @@ failure_route[1] {
|
|
|
|
|
|
|
|
|
|
This function can be used from REQUEST_ROUTE and FAILURE_ROUTE.
|
|
|
|
|
|
|
|
|
|
Example 1.76. t_load_contacts usage
|
|
|
|
|
Example 1.77. t_load_contacts usage
|
|
|
|
|
...
|
|
|
|
|
if (!t_load_contacts()) {
|
|
|
|
|
sl_send_reply("500", "Server Internal Error - Cannot load contacts");
|
|
|
|
|
@ -2402,7 +2418,7 @@ if (!t_load_contacts()) {
|
|
|
|
|
contact_flows_avp are not anymore set. Based on that test, you can then
|
|
|
|
|
use t_set_fr() function to set timers according to your needs.
|
|
|
|
|
|
|
|
|
|
Example 1.77. t_next_contacts usage
|
|
|
|
|
Example 1.78. t_next_contacts usage
|
|
|
|
|
...
|
|
|
|
|
# First call after t_load_contacts() when transaction does not exist yet
|
|
|
|
|
# and contacts should be available
|
|
|
|
|
@ -2439,7 +2455,7 @@ if (!t_next_contacts()) {
|
|
|
|
|
thus there was nothing to do, and returns -1 in case of an error (see
|
|
|
|
|
syslog). This function can be used from a BRANCH_FAILURE event route.
|
|
|
|
|
|
|
|
|
|
Example 1.78. t_next_contact_flow usage
|
|
|
|
|
Example 1.79. t_next_contact_flow usage
|
|
|
|
|
...
|
|
|
|
|
event_route[tm:branch-failure:outbound]
|
|
|
|
|
{
|
|
|
|
|
@ -2462,7 +2478,7 @@ event_route[tm:branch-failure:outbound]
|
|
|
|
|
|
|
|
|
|
This function can be used from ANY_ROUTE .
|
|
|
|
|
|
|
|
|
|
Example 1.79. t_check_status usage
|
|
|
|
|
Example 1.80. t_check_status usage
|
|
|
|
|
...
|
|
|
|
|
if (t_check_status("(487)|(408)")) {
|
|
|
|
|
log("487 or 408 negative reply\n");
|
|
|
|
|
@ -2516,7 +2532,7 @@ Note
|
|
|
|
|
|
|
|
|
|
See also: t_lookup_request(), t_lookup_cancel().
|
|
|
|
|
|
|
|
|
|
Example 1.80. t_check_trans usage
|
|
|
|
|
Example 1.81. t_check_trans usage
|
|
|
|
|
if ( method == "CANCEL" && !t_check_trans())
|
|
|
|
|
sl_reply("403", "cancel out of the blue forbidden");
|
|
|
|
|
# note: in this example t_check_trans() can be replaced by t_lookup_cancel()
|
|
|
|
|
@ -2531,7 +2547,7 @@ if ( method == "CANCEL" && !t_check_trans())
|
|
|
|
|
|
|
|
|
|
See also: disable_6xx_block.
|
|
|
|
|
|
|
|
|
|
Example 1.81. t_set_disable_6xx usage
|
|
|
|
|
Example 1.82. t_set_disable_6xx usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2546,7 +2562,7 @@ route {
|
|
|
|
|
|
|
|
|
|
See also: use_dns_failover.
|
|
|
|
|
|
|
|
|
|
Example 1.82. t_set_disable_failover usage
|
|
|
|
|
Example 1.83. t_set_disable_failover usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2559,7 +2575,7 @@ route {
|
|
|
|
|
|
|
|
|
|
Turn off/on sending internally a SIP reply in case of relay errors.
|
|
|
|
|
|
|
|
|
|
Example 1.83. t_set_disable_internal_reply usage
|
|
|
|
|
Example 1.84. t_set_disable_internal_reply usage
|
|
|
|
|
...
|
|
|
|
|
t_set_disable_internal_reply(1); # turn off sending internal reply on error
|
|
|
|
|
if(!t_relay()) {
|
|
|
|
|
@ -2590,7 +2606,7 @@ if(!t_relay()) {
|
|
|
|
|
* hostport - address in "host:port" format. It can be given via an
|
|
|
|
|
AVP.
|
|
|
|
|
|
|
|
|
|
Example 1.84. t_replicate usage
|
|
|
|
|
Example 1.85. t_replicate usage
|
|
|
|
|
...
|
|
|
|
|
# sent to 1.2.3.4:5060 over tcp
|
|
|
|
|
t_replicate("sip:1.2.3.4:5060;transport=tcp");
|
|
|
|
|
@ -2624,7 +2640,7 @@ t_replicate_to_udp("1.2.3.4", "5060");
|
|
|
|
|
+ 0x02 - do not generate reply on internal error.
|
|
|
|
|
+ 0x04 - disable dns failover.
|
|
|
|
|
|
|
|
|
|
Example 1.85. t_relay_to usage
|
|
|
|
|
Example 1.86. t_relay_to usage
|
|
|
|
|
...
|
|
|
|
|
# sent to 1.2.3.4:5060 over tcp
|
|
|
|
|
t_relay_to("tcp:1.2.3.4:5060");
|
|
|
|
|
@ -2647,7 +2663,7 @@ t_relay_to("0x01");
|
|
|
|
|
|
|
|
|
|
See also: e2e_cancel_reason.
|
|
|
|
|
|
|
|
|
|
Example 1.86. t_set_no_e2e_cancel_reason usage
|
|
|
|
|
Example 1.87. t_set_no_e2e_cancel_reason usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
...
|
|
|
|
|
@ -2670,7 +2686,7 @@ opying
|
|
|
|
|
* onreply_route - the function returns true if an onreply route is
|
|
|
|
|
set to be executed.
|
|
|
|
|
|
|
|
|
|
Example 1.87. t_replicate usage
|
|
|
|
|
Example 1.88. t_replicate usage
|
|
|
|
|
...
|
|
|
|
|
if(!t_is_set("failure_route"))
|
|
|
|
|
LM_DBG("no failure route will be executed for current transaction\n");
|
|
|
|
|
@ -2684,7 +2700,7 @@ if(!t_is_set("failure_route"))
|
|
|
|
|
|
|
|
|
|
It returns true.
|
|
|
|
|
|
|
|
|
|
Example 1.88. t_use_uac_headers usage
|
|
|
|
|
Example 1.89. t_use_uac_headers usage
|
|
|
|
|
...
|
|
|
|
|
t_use_uac_headers();
|
|
|
|
|
...
|
|
|
|
|
@ -2703,7 +2719,7 @@ t_use_uac_headers();
|
|
|
|
|
returns true if the transaction is currently reply suspended or false
|
|
|
|
|
if not.
|
|
|
|
|
|
|
|
|
|
Example 1.89. t_is_retr_async_reply usage
|
|
|
|
|
Example 1.90. t_is_retr_async_reply usage
|
|
|
|
|
...
|
|
|
|
|
if (t_is_retr_async_reply()) {
|
|
|
|
|
xlog("L_DBG", "Dropping retransmitted reply which is still currently sus
|
|
|
|
|
@ -2893,7 +2909,7 @@ action *route)
|
|
|
|
|
enabled with the t_on_branch_failure function. This event_route uses
|
|
|
|
|
the BRANCH_FAILURE_ROUTE route type.
|
|
|
|
|
|
|
|
|
|
Example 1.90. event_route[tm:branch-failure] usage
|
|
|
|
|
Example 1.91. event_route[tm:branch-failure] usage
|
|
|
|
|
...
|
|
|
|
|
route {
|
|
|
|
|
t_on_branch_failure("myroute");
|
|
|
|
|
|
Victor Seva
10 years ago