Kamailio 3.1.2
I am testing out dialplan module. Every time when I issue 'kamctl dialplan show', it shows what is in the database even if I have not yet issue "kamctl dialplan reload' after I changed data in database. I thought that dialplan is stored in the memory and you have to issue the reload before you can see the change. Why the ' kamctl dialplan show' display the data directly from mysql database? Does that mean that dialplan data is not stored in the memory?
Gary
Hi All,
I'm having doubts in the implementation of the callback function module tm.
As she calls the function to record register_tmcb ()?
Can someome help me?
Regards
I am talking about kamctl dialplan command not mi.
When you type in kamctl, it lists a lot commands. Are these commands still valid?
See below:
kamctl
../../sbin/kamctl 3.1.0
Existing commands:
-- command 'start|stop|restart'
restart ............................ restart Kamailio
start .............................. start Kamailio
stop ............................... stop Kamailio
-- command 'acl' - manage access control lists (acl)
acl show [<username>] .............. show user membership
acl grant <username> <group> ....... grant user membership (*)
acl revoke <username> [<group>] .... grant user membership(s) (*)
-- command 'lcr' - manage least cost routes (lcr)
lcr show_gws....... show database gateways
lcr show_routes.... show database routes
lcr dump_gws....... show in memory gateways
lcr dump_routes.... show in memory routes
lcr reload ........ reload lcr gateways and routes
lcr eval_weights .. evaluates probability for given GW's weights
-- command 'cr' - manage carrierroute tables
cr show ....................................................... show tables
cr reload ..................................................... reload tables
cr dump ....................................................... show in memory tables
cr addcn <carrier id> <carrier name> .......................... add a carrier name
cr rmcn <carrier id> ......................................... rm a carrier name
cr adddn <domain id> <domain name> ............................ add a domain name
cr rmdn <domain id> .......................................... rm a domain name
cr addcarrier <carrier> <scan_prefix> <domain> <rewrite_host> ................
<prob> <strip> <rewrite_prefix> <rewrite_suffix> ...............
<flags> <mask> <comment> .........................add a carrier
(prob, strip, rewrite_prefix, rewrite_suffix,...................
flags, mask and comment are optional arguments) ...............
cr rmcarrier <carrier> <scan_prefix> <domain> ................ rm a carrier
-- command 'rpid' - manage Remote-Party-ID (RPID)
rpid add <username> <rpid> ......... add rpid for a user (*)
rpid rm <username> ................. set rpid to NULL for a user (*)
rpid show <username> ............... show rpid of a user
-- command 'add|passwd|rm' - manage subscribers
add <username> <password> .......... add a new subscriber (*)
passwd <username> <passwd> ......... change user's password (*)
rm <username> ...................... delete a user (*)
-- command 'add|dump|reload|rm|show' - manage trusted
trusted show ...................... show db content
trusted dump ...................... show cache content
trusted reload .................... reload db table into cache
trusted add <src_ip> <proto> <from_pattern> <tag>
....................... add a new entry
....................... (from_pattern and tag are optional arguments)
trusted rm <src_ip> ............... remove all entres for the given src_ip
-- command 'dispatcher' - manage dispatcher
* Examples: dispatcher addgw 1 sip:1.2.3.1:5050 1 'outbound gateway'
* dispatcher addgw 2 sip:1.2.3.4:5050 3 ''
* dispatcher rmgw 4
dispatcher show ..................... show dispatcher gateways
dispatcher reload ................... reload dispatcher gateways
dispatcher dump ..................... show in memory dispatcher gateways
dispatcher addgw <setid> <destination> <flags> <description>
.......................... add gateway
dispatcher rmgw <id> ................ delete gateway
-- command 'db' - database operations
db exec <query> ..................... execute SQL query
db roexec <roquery> ................. execute read-only SQL query
db run <id> ......................... execute SQL query from $id variable
db rorun <id> ....................... execute read-only SQL query from
$id variable
db show <table> ..................... display table content
-- command 'speeddial' - manage speed dials (short numbers)
speeddial show <speeddial-id> ....... show speeddial details
speeddial list <sip-id> ............. list speeddial for uri
speeddial add <sip-id> <sd-id> <new-uri> [<desc>] ...
........................... add a speedial (*)
speeddial rm <sip-id> <sd-id> ....... remove a speeddial (*)
speeddial help ...................... help message
- <speeddial-id>, <sd-id> must be an AoR (username@domain)
- <sip-id> must be an AoR (username@domain)
- <new-uri> must be a SIP AoR (sip:username@domain)
- <desc> a description for speeddial
-- command 'avp' - manage AVPs
avp list [-T table] [-u <sip-id|uuid>]
[-a attribute] [-v value] [-t type] ... list AVPs
avp add [-T table] <sip-id|uuid>
<attribute> <type> <value> ............ add AVP (*)
avp rm [-T table] [-u <sip-id|uuid>]
[-a attribute] [-v value] [-t type] ... remove AVP (*)
avp help .................................. help message
- -T - table name
- -u - SIP id or unique id
- -a - AVP name
- -v - AVP value
- -t - AVP name and type (0 (str:str), 1 (str:int),
2 (int:str), 3 (int:int))
- <sip-id> must be an AoR (username@domain)
- <uuid> must be a string but not AoR
-- command 'alias_db' - manage database aliases
alias_db show <alias> .............. show alias details
alias_db list <sip-id> ............. list aliases for uri
alias_db add <alias> <sip-id> ...... add an alias (*)
alias_db rm <alias> ................ remove an alias (*)
alias_db help ...................... help message
- <alias> must be an AoR (username@domain)"
- <sip-id> must be an AoR (username@domain)"
-- command 'domain' - manage local domains
domain reload ....................... reload domains from disk
domain show ......................... show current domains in memory
domain showdb ....................... show domains in the database
domain add <domain> ................. add the domain to the database
domain rm <domain> .................. delete the domain from the database
-- command 'cisco_restart' - restart CISCO phone (NOTIFY)
cisco_restart <uri> ................ restart phone configured for <uri>
-- command 'online' - dump online users from memory
online ............................. display online users
-- command 'monitor' - show internal status
monitor ............................ show server's internal status
-- command 'ping' - ping a SIP URI (OPTIONS)
ping <uri> ......................... ping <uri> with SIP OPTIONS
-- command 'ul|alias' - manage user location or aliases
ul show [<username>]................ show in-RAM online users
ul show --brief..................... show in-RAM online users in short format
ul rm <username> [<contact URI>].... delete user's usrloc entries
ul add <username> <uri> ............ introduce a permanent usrloc entry
ul add <username> <uri> <expires> .. introduce a temporary usrloc entry
-- command 'fifo'
fifo ............................... send raw FIFO command
-- command 'cisco_restart' - restart CISCO phone (NOTIFY)
cisco_restart <uri> ................ restart phone configured for <uri>
-- command 'online' - dump online users from memory
online ............................. display online users
-- command 'monitor' - show internal status
monitor ............................ show server's internal status
-- command 'ping' - ping a SIP URI (OPTIONS)
ping <uri> ......................... ping <uri> with SIP OPTIONS
-- command 'ul|alias' - manage user location or aliases
ul show [<username>]................ show in-RAM online users
ul show --brief..................... show in-RAM online users in short format
ul rm <username> [<contact URI>].... delete user's usrloc entries
ul add <username> <uri> ............ introduce a permanent usrloc entry
ul add <username> <uri> <expires> .. introduce a temporary usrloc entry
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Juha Heinanen
Sent: Friday, June 03, 2011 3:50 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List
Subject: [SR-Users] Questino about dialplan module
Gary Chen writes:
> I am testing out dialplan module. Every time when I issue 'kamctl
> dialplan show', it shows what is in the database even if I have not
> yet issue "kamctl dialplan reload' after I changed data in database. I
> thought that dialplan is stored in the memory and you have to issue
> the reload before you can see the change. Why the ' kamctl dialplan
> show' display the data directly from mysql database? Does that mean
> that dialplan data is not stored in the memory?
there is no mi function to show dialplan rules in memory. i have no
idea, what 'show' does. please read readme of dialplan module before
asking questions about the module.
-- juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
there is a bug in IMC module that crashes Kamailio.
Here is the scenario: One user (pero(a)abc.hr) creates private chat room (
chat-999(a)abc.hr). Other user (oz(a)abc.hr) tries to join the
chat-999(a)abc.hrby sending #join. Kamailio crashes at that point. Here
is the log:
Best regards,
Ozren
Jun 1 15:10:37 ser-test kernel: [5844312.456709] kamailio[20118]: segfault
at 10 ip 7f28f89dae8e sp 7fffffffb750 error 4 in imc.so[7f28f89cf000+17000]
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20118]:
INFO: <script>: going to imc: F [sip:oz@abc.hr] T [sip:chat-999@abc.hr] B
[#join]
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [receive.c:186]: preparing to run routing scripts...
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20118]:
DEBUG: imc [imc.c:525]: found command
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: maxfwd [mf_funcs.c:85]: value = 70
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20118]:
DEBUG: imc [imc_cmd.c:146]: command: [join]
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [parser/msg_parser.c:201]: DEBUG: get_hdr_body :
content_length=223
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20118]:
DEBUG: imc [imc_cmd.c:292]: found room [chat-999]
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [parser/msg_parser.c:103]: found end of header
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20118]:
ERROR: imc [imc_cmd.c:317]: attept to join private room [chat-999] from user
[oz]
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [parser/parse_to.c:174]: DEBUG: add_param: tag=5e3288a6
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
ALERT: <core> [main.c:741]: child process 20118 exited by a signal 11
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [parser/parse_to.c:803]: end of header reached, state=29
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20119]:
DEBUG: <core> [parser/msg_parser.c:630]: SIP Request:
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
ALERT: <core> [main.c:744]: core was not generated
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20121]:
DEBUG: <core> [msg_translator.c:204]: check_via_address(161.53.255.82,
161.53.255.82, 0)
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20119]:
DEBUG: <core> [parser/msg_parser.c:632]: method: <MESSAGE>
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20114]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20115]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20116]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20117]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20122]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20124]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20125]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20129]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20128]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20127]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20123]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20126]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20120]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20130]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20131]:
INFO: <core> [main.c:807]: INFO: signal 15 received
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
DEBUG: imc [imc.c:709]: room 3 chat-777
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
DEBUG: imc [imc.c:709]: room 11 chat-888
Jun 1 15:10:37 ser-test /usr/local/kamailio-ozren/sbin/kamailio[20113]:
DEBUG: imc [imc.c:709]: room 13 chat-999
On 18 April 2011 15:47, Henning Westerholt <henning.westerholt(a)1und1.de> wrote:
> On Monday 18 April 2011, Roman Yeryomin wrote:
>> coredump? easy :)
>> you can pick core file itself here (it's pretty heavy to send to the list):
>> http://83.99.159.113/core.kamailio.20110418-1331
>>
>> What do you mean by backtrace? log output or strace output?
>
> Hi Roman,
>
> he refers to a gdb backtrace, "gdb bt". More informations e.g. here:
> http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:corefiles
>
ok, here is the backtrace:
# gdb kamailio core
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done.
Loaded symbols for /lib/tls/i686/cmov/libdl.so.2
Reading symbols from /lib/tls/i686/cmov/libresolv.so.2...done.
Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2
Reading symbols from /lib/tls/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/tls/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/local/lib/kamailio/modules_k/mi_fifo.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/mi_fifo.so
Reading symbols from /usr/local/lib/kamailio/libkmi.so.1...done.
Loaded symbols for /usr/local/lib/kamailio/libkmi.so.1
Reading symbols from /usr/local/lib/kamailio/modules_k/kex.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/kex.so
Reading symbols from /usr/local/lib/kamailio/libkcore.so.1...done.
Loaded symbols for /usr/local/lib/kamailio/libkcore.so.1
Reading symbols from /usr/local/lib/kamailio/modules/tm.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/tm.so
Reading symbols from /usr/local/lib/kamailio/modules_k/tmx.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/tmx.so
Reading symbols from /usr/local/lib/kamailio/modules/sl.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/sl.so
Reading symbols from /usr/local/lib/kamailio/modules_k/rr.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/rr.so
Reading symbols from /usr/local/lib/kamailio/modules_k/pv.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/pv.so
Reading symbols from /usr/local/lib/kamailio/modules_k/maxfwd.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/maxfwd.so
Reading symbols from /usr/local/lib/kamailio/modules_k/usrloc.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/usrloc.so
Reading symbols from /usr/local/lib/kamailio/libsrdb1.so.1...done.
Loaded symbols for /usr/local/lib/kamailio/libsrdb1.so.1
Reading symbols from /usr/local/lib/kamailio/modules_k/registrar.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/registrar.so
Reading symbols from /usr/local/lib/kamailio/modules_k/textops.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/textops.so
Reading symbols from /usr/local/lib/kamailio/modules_k/siputils.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/siputils.so
Reading symbols from /usr/local/lib/kamailio/modules_k/xlog.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/xlog.so
Reading symbols from /usr/local/lib/kamailio/modules/sanity.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/sanity.so
Reading symbols from /usr/local/lib/kamailio/modules/ctl.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/ctl.so
Reading symbols from /usr/local/lib/kamailio/modules/mi_rpc.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/mi_rpc.so
Reading symbols from /usr/local/lib/kamailio/modules_k/acc.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/acc.so
Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...done.
Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0
Reading symbols from /usr/local/lib/kamailio/modules_k/perl.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/perl.so
Reading symbols from /usr/lib/libperl.so.5.8...done.
Loaded symbols for /usr/lib/libperl.so.5.8
Reading symbols from /lib/tls/i686/cmov/libm.so.6...done.
Loaded symbols for /lib/tls/i686/cmov/libm.so.6
Reading symbols from /lib/tls/i686/cmov/libcrypt.so.1...done.
Loaded symbols for /lib/tls/i686/cmov/libcrypt.so.1
Reading symbols from /usr/local/lib/kamailio/modules_k/perlvdb.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/perlvdb.so
Reading symbols from /usr/local/lib/kamailio/modules/auth.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/auth.so
Reading symbols from /usr/local/lib/kamailio/modules_k/auth_db.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/auth_db.so
Reading symbols from /usr/local/lib/kamailio/modules/app_lua.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules/app_lua.so
Reading symbols from /usr/lib/liblua5.1.so.0...done.
Loaded symbols for /usr/lib/liblua5.1.so.0
Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done.
Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2
Reading symbols from /lib/tls/i686/cmov/libnss_dns.so.2...done.
Loaded symbols for /lib/tls/i686/cmov/libnss_dns.so.2
Core was generated by `kamailio -dddd'.
Program terminated with signal 11, Segmentation fault.
[New process 13773]
#0 0xb7228e3a in parseurl (url=0xb7213230 "T�0\b#") at perlvdbfunc.c:60
60 if (strlen(cn) > 0)
If I understand this correctly error refers to row 60 in perlvdbfunc.c
strlen expects const char* instead of char* ?
Regards,
Roman
That works. Thanks.
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, June 02, 2011 4:28 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
Cc: Gary Chen
Subject: Re: [SR-Users] Problem using dispatcher.
On 6/2/11 9:41 PM, Gary Chen wrote:
Thanks for the quick reply.
How can I fix this?
When you set t_on_failure for an INVITE, the respective failure route will be executed for any reply >=0. What you have to do is to not re-route to a new destination from failure route, simply exit for those reply codes, like:
if(t_check_status("401|407")) exit;
You don't handle as well the canceled transactions, when re-routing makes no sense -- you should do it (see default config file for example.
Cheers,
Daniel
We are using Kamailio as single point of entry for all our phones. Our phones all registered with Freeswitch. Kamailio only route the SIP traffic. Is there any way I can make Kamailio not treat 407 as failure?
I also have the same problem with REGISTER messages when Freeswitch reply with '401 Unauthorized'. I end up using Forward() instead of t_relay() to make the phone1 register with Freeswitch.
Any suggestion?
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org [ mailto:sr-users-bounces@lists.sip-router.org ] On Behalf Of Alex Balashov
Sent: Thursday, June 02, 2011 3:30 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Problem using dispatcher.
On 06/02/2011 03:26 PM, Gary Chen wrote:
> the dispatcher always get into FAILURE route although the log shows
> that kamailio did send INVITE to 10.10.1.222 and received '407 -
> Proxy Authentication Required' from Freexwitch1 and then dispatcher
> send INVITE to 10.10.1.223 and also received '407 - Proxy
> Authentication Required' from Freexwitch2 and eventually failed.
That's because any reply >= 300 is considered a failure.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Thanks for the quick reply.
How can I fix this?
We are using Kamailio as single point of entry for all our phones. Our phones all registered with Freeswitch. Kamailio only route the SIP traffic. Is there any way I can make Kamailio not treat 407 as failure?
I also have the same problem with REGISTER messages when Freeswitch reply with '401 Unauthorized'. I end up using Forward() instead of t_relay() to make the phone1 register with Freeswitch.
Any suggestion?
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov
Sent: Thursday, June 02, 2011 3:30 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Problem using dispatcher.
On 06/02/2011 03:26 PM, Gary Chen wrote:
> the dispatcher always get into FAILURE route although the log shows
> that kamailio did send INVITE to 10.10.1.222 and received '407 -
> Proxy Authentication Required' from Freexwitch1 and then dispatcher
> send INVITE to 10.10.1.223 and also received '407 - Proxy
> Authentication Required' from Freexwitch2 and eventually failed.
That's because any reply >= 300 is considered a failure.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
we should decide the roadmap to next major release v3.2.0, so probably
an IRC meeting for some real time chatting would be good. I am thinking
of June 3 or 4, 15:00GMT. Anyone interested in the meeting and available
in one of those dates? The date with most of devs available will be
selected.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda
