20 Jun
2011
20 Jun
'11
1:41 p.m.
Hello,
I just wanted to mark the 15000th development commit in our project
(counted only on GIT master branch). It happened several days ago and it
was done by the same person that did the first commit, Andrei:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -1
512dcd9 Andrei Pelinescu-Onciul Mon Sep 3 21:27:11 2001 +0000
Initial revision
The 15000th one is:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -15000
| tail -1
8a90dd3 Andrei Pelinescu-Onciul Sat Jun 11 11:24:05 2011 +0200
core: remove unused variables + coding style
I published the news about it on project sites as well:
* http://asipto.com/u/37
* http://asipto.com/u/38
Now it's the time to look forward to the 20000th commit!
Enjoy the summer, autumn comes with v3.2.0,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
20 Jun
20 Jun
1:37 p.m.
New subject: [Kamailio-Business] The 15000th development commit
congratulation Andrei !
20000TH would by you, daniel ;)
----- Original Message -----
From: "Daniel-Constantin Mierla" <miconda(a)gmail.com>
To: "kamailio" <sr-users(a)lists.sip-router.org>rg>; "sr-dev"
<sr-dev(a)lists.sip-router.org>rg>; <business(a)lists.kamailio.org>
Sent: Monday, June 20, 2011 3:41 PM
Subject: [Kamailio-Business] The 15000th development commit
Hello,
I just wanted to mark the 15000th development commit in our project
(counted only on GIT master branch). It happened several days ago and it
was done by the same person that did the first commit, Andrei:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -1
512dcd9 Andrei Pelinescu-Onciul Mon Sep 3 21:27:11 2001 +0000
Initial revision
The 15000th one is:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -15000 |
tail -1
8a90dd3 Andrei Pelinescu-Onciul Sat Jun 11 11:24:05 2011 +0200
core: remove unused variables + coding style
I published the news about it on project sites as well:
* http://asipto.com/u/37
* http://asipto.com/u/38
Now it's the time to look forward to the 20000th commit!
Enjoy the summer, autumn comes with v3.2.0,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
Kamailio (OpenSER) - Business mailing list
Business(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/business
http://lists.openser-project.org/cgi-bin/mailman/listinfo/business
__________ Information provenant d'ESET NOD32 Antivirus, version de la
base des signatures de virus 6222 (20110620) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des
signatures de virus 6223 (20110620) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com
21 Jun
21 Jun
8:27 a.m.
New subject: [Kamailio-Business] The 15000th development commit
On 6/20/11 3:37 PM, Meftah Tayeb wrote:
congratulation Andrei !
20000TH would by you, daniel ;)
I did the commit no 14892, so the 20k-th is someone
else turn :-)
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -14892
| tail -1
d4a66da Daniel-Constantin Mierla Mon Apr 25 12:23:46 2011 +0200
kex: added mi cmd clear_statistics
Cheers,
Daniel
----- Original Message ----- From: "Daniel-Constantin Mierla"
<miconda(a)gmail.com>
To: "kamailio" <sr-users(a)lists.sip-router.org>rg>; "sr-dev"
<sr-dev(a)lists.sip-router.org>rg>; <business(a)lists.kamailio.org>
Sent: Monday, June 20, 2011 3:41 PM
Subject: [Kamailio-Business] The 15000th development commit
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello,
I just wanted to mark the 15000th development commit in our project
(counted only on GIT master branch). It happened several days ago and
it was done by the same person that did the first commit, Andrei:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head -1
512dcd9 Andrei Pelinescu-Onciul Mon Sep 3 21:27:11 2001 +0000
Initial revision
The 15000th one is:
git log --pretty=format:"%h%x09%an%x09%ad%x09%s" --reverse | head
-15000 | tail -1
8a90dd3 Andrei Pelinescu-Onciul Sat Jun 11 11:24:05 2011 +0200
core: remove unused variables + coding style
I published the news about it on project sites as well:
* http://asipto.com/u/37
* http://asipto.com/u/38
Now it's the time to look forward to the 20000th commit!
Enjoy the summer, autumn comes with v3.2.0,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
Kamailio (OpenSER) - Business mailing list
Business(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/business
http://lists.openser-project.org/cgi-bin/mailman/listinfo/business
__________ Information provenant d'ESET NOD32 Antivirus, version de
la base des signatures de virus 6222 (20110620) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com
__________ Information provenant d'ESET NOD32 Antivirus, version de la
base des signatures de virus 6223 (20110620) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.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 
9:03 a.m.
New subject: kamailio realtime integration
Hello all,
I want to use realtime architecture kamailio 3.1 + asterisk 1.6.2
described at
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb,
but use it with another softswitch (it also use mysql db for configuration).
If it possible please answer for several questions:
1. What is "#!define WITH_ASTERISK" option doing ?
Does it only use for:
- load uac module
- read login\passw table info
- some routing cases
or there are some else jobs ?
Maybe there is some description for "#!define WITH_ASTERISK" ?
2. What else fields of asterisk realtime table (except
username\sippasswd) kamailio uses for integration ?
3. From integration manual:
"
CREATE TABLE version (
table_name VARCHAR(32) NOT NULL,
table_version INT UNSIGNED DEFAULT 0 NOT NULL
);
INSERT INTO version (table_name, table_version) VALUES
('sipusers','6');
"
For what purposes this table used ? How to change it for using with
another softswitch ?
--
vf
9:55 a.m.
New subject: kamailio realtime integration
Hello,
On 6/21/11 11:03 AM, vaad.fabi(a)gmail.com wrote:
Hello all,
I want to use realtime architecture kamailio 3.1 + asterisk 1.6.2
described at
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb,
but use it with another softswitch (it also use mysql db for
configuration).
If it possible please answer for several questions:
1. What is "#!define WITH_ASTERISK" option doing ?
Does it only use for:
- load uac module
- read login\passw table info
- some routing cases
or there are some else jobs ?
Maybe there is some description for "#!define WITH_ASTERISK" ?
#!define XYZ - is a config preprocessor directive that can be used to
set a value for a token or enable/disable parts of configuration file.
In this particular case if #!define WITH_ASTERISK is not in the config,
all the parts between:
#!ifdef WITH_ASTERISK
...
#!endif
will be ignored by kamailio.
2. What else fields of asterisk realtime table (except
username\sippasswd) kamailio uses for integration ?
This two are enough for
authentication.
3. From integration manual:
"
CREATE TABLE version (
table_name VARCHAR(32) NOT NULL,
table_version INT UNSIGNED DEFAULT 0 NOT NULL
);
INSERT INTO version (table_name, table_version) VALUES
('sipusers','6');
"
For what purposes this table used ? How to change it for using with
another softswitch ?
This table is required by kamailio to check the version of
tables used
internally - default one for this case would be subscriber table, but
since it connects to asterisk database and uses instead the sipusers
table, it has to be able to see that the version for sipusers table
structure is 6.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
10:17 a.m.
New subject: kamailio realtime integration
On 06/21/2011 12:55 PM, Daniel-Constantin Mierla wrote:
Daniel, thanx for your help and wonderful software!
I want to use different table structure (non asterisk) for integration,
and the questions are:
- what sipusers table fields it uses (only username\sippasswd or some
else)
- where kamailio save registration information (in sipusers or in
another own table)
--
vf
3. From integration manual:
"
CREATE TABLE version (
table_name VARCHAR(32) NOT NULL,
table_version INT UNSIGNED DEFAULT 0 NOT NULL
);
INSERT INTO version (table_name, table_version) VALUES
('sipusers','6');
"
For what purposes this table used ? How to change it for using with
another softswitch ?
This table is required by kamailio to check the version of
tables used
internally - default one for this case would be subscriber table, but
since it connects to asterisk database and uses instead the sipusers
table, it has to be able to see that the version for sipusers table
structure is 6.
Cheers,
Daniel
12:30 p.m.
New subject: kamailio realtime integration
On 6/21/11 12:17 PM, vaad.fabi(a)gmail.com wrote:
On 06/21/2011 12:55 PM, Daniel-Constantin Mierla
wrote:
Daniel, thanx for your help and wonderful software!
I want to use different table structure (non asterisk) for
integration, and the questions are:
- what sipusers table fields it uses (only username\sippasswd or some
else)
only these two,
3. From integration manual:
"
CREATE TABLE version (
table_name VARCHAR(32) NOT NULL,
table_version INT UNSIGNED DEFAULT 0 NOT NULL
);
INSERT INTO version (table_name, table_version) VALUES
('sipusers','6');
"
For what purposes this table used ? How to change it for using with
another softswitch ?
This table is required by kamailio to check the version of
tables
used internally - default one for this case would be subscriber
table, but since it connects to asterisk database and uses instead
the sipusers table, it has to be able to see that the version for
sipusers table structure is 6.
Cheers,
Daniel - where kamailio save registration information (in
sipusers or in
another own table)
it keeps in its own 'location' table located in openser
database.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
24 Jun
24 Jun
8:01 a.m.
New subject: kamailio realtime integration
Hi all,
Still trying to run kamailio 3.1.x + asterisk 1.6.2.X realtime architecture.
As i mentioned earlier, instead of asterisk i use another softswitch
with db, table "retailroute" with "login" and "password"
fields as user
auth data.
Of course, troubles... user can't register to kamailio :(
Logs( without users attempts to register, only kamailio internal logic:
Jun 24 11:23:26 sbc kamailio[17768]: INFO: <script>: ------------------
SIP Request: method [NOTIFY] from [sip:100@100.100.100.100] to
[sip:100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:167]: get_hdr_field: cseq <CSeq>: <811> <NOTIFY>
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: maxfwd [mf_funcs.c:85]:
value = 70
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:201]: DEBUG: get_hdr_body : content_length=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:103]: found end of header
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX, 192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: siputils [checks.c:73]: no
totag
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1081]: DEBUG:
t_check_msg: msg id=39 global id=38 T start=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:528]:
t_lookup_request: start searching: hash=31430, isACK=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:485]: DEBUG:
RFC3261 transaction matching failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:711]: DEBUG:
t_lookup_request: no transaction found
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1150]: DEBUG:
t_check_msg: msg id=39 global id=39 T end=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [select.c:424]:
Calling SELECT 0x832b7e4
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [socket_info.c:501]:
grep_sock_info - checking if host==us: 13==13 && [100.100.100.100] ==
[100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [socket_info.c:504]:
grep_sock_info - checking if port 5060 matches port 5060
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db [authorize.c:239]:
realm value [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:95]: auth:
digest-algo: MD5 parsed value: 1
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:118]:
allocate 28 bytes for result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:68]: 1
columns returned from the query
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:155]:
allocate 4 bytes for result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:165]:
allocate 4 bytes for result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:85]:
allocate 8 bytes for RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:92]:
RES_NAMES(0x832c950)[0]=[password]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:136]: use
DB1_STRING result type
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:184]:
allocate 8 bytes for rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:119]:
allocate 20 bytes for row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_val.c:117]:
converting STRING [dav0011]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db [authorize.c:120]:
HA1 string calculated: a8fdf502e497ff8e9407ac2dc31540df
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:205]:
check_response: Our result = 'fa83bf7c0a7af33cc500aa2b62758931'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:215]:
check_response: Authorization failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:81]:
freeing 1 columns
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:85]:
freeing RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:94]:
freeing result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:99]:
freeing result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:54]:
freeing 1 rows
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:97]:
freeing row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:62]:
freeing rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:136]:
freeing result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:102]:
build_challenge_hf: realm='100.100.100.100'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:236]:
auth: 'Proxy-Authenticate: Digest realm="100.100.100.100",
nonce="TgQ8mU4EO22Odd1W63tOO27IRrKX0kU '
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: sl [sl.c:278]: reply in
stateless mode (sl)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX, 192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [usr_avp.c:646]:
DEBUG:destroy_avp_list: destroying list (nil)
Such messages periodically sends kamailio. Why kamailio every time sends
yourself these NOTIFY messages, what it try to do ?
I see problem something around auth_db autorization and HA1, isn't it ?
How to fix it ?
--
Vadim F.
9 a.m.
New subject: kamailio realtime integration
Hello,
based on the logs, the authentication fails due to wrong password. Check
that you have the right password on client side.
Kamailio does not generate any NOTIFY unless the presence server modules
are loaded. If not, then the notify comes from somewhere else and it is
just looped back due to config file routing logic.
Cheers,
Daniel
On 6/24/11 10:01 AM, vaad.fabi(a)gmail.com wrote:
Hi all,
Still trying to run kamailio 3.1.x + asterisk 1.6.2.X realtime
architecture.
As i mentioned earlier, instead of asterisk i use another softswitch
with db, table "retailroute" with "login" and "password"
fields as
user auth data.
Of course, troubles... user can't register to kamailio :(
Logs( without users attempts to register, only kamailio internal logic:
Jun 24 11:23:26 sbc kamailio[17768]: INFO: <script>:
------------------ SIP Request: method [NOTIFY] from
[sip:100@100.100.100.100] to [sip:100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:167]: get_hdr_field: cseq <CSeq>: <811> <NOTIFY>
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: maxfwd [mf_funcs.c:85]:
value = 70
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:201]: DEBUG: get_hdr_body : content_length=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:103]: found end of header
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: siputils [checks.c:73]: no
totag
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1081]:
DEBUG: t_check_msg: msg id=39 global id=38 T start=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:528]:
t_lookup_request: start searching: hash=31430, isACK=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:485]:
DEBUG: RFC3261 transaction matching failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:711]:
DEBUG: t_lookup_request: no transaction found
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1150]:
DEBUG: t_check_msg: msg id=39 global id=39 T end=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [select.c:424]:
Calling SELECT 0x832b7e4
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:501]: grep_sock_info - checking if host==us: 13==13 &&
[100.100.100.100] == [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:504]: grep_sock_info - checking if port 5060 matches
port 5060
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db [authorize.c:239]:
realm value [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:95]: auth:
digest-algo: MD5 parsed value: 1
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:118]:
allocate 28 bytes for result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:68]: 1
columns returned from the query
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:155]:
allocate 4 bytes for result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:165]:
allocate 4 bytes for result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:85]:
allocate 8 bytes for RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:92]:
RES_NAMES(0x832c950)[0]=[password]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:136]:
use DB1_STRING result type
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:184]:
allocate 8 bytes for rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:119]:
allocate 20 bytes for row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_val.c:117]:
converting STRING [dav0011]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db [authorize.c:120]:
HA1 string calculated: a8fdf502e497ff8e9407ac2dc31540df
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:205]:
check_response: Our result = 'fa83bf7c0a7af33cc500aa2b62758931'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:215]:
check_response: Authorization failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:81]:
freeing 1 columns
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:85]:
freeing RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:94]:
freeing result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:99]:
freeing result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:54]:
freeing 1 rows
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:97]:
freeing row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:62]:
freeing rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:136]:
freeing result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:102]:
build_challenge_hf: realm='100.100.100.100'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:236]:
auth: 'Proxy-Authenticate: Digest realm="100.100.100.100",
nonce="TgQ8mU4EO22Odd1W63tOO27IRrKX0kU '
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: sl [sl.c:278]: reply in
stateless mode (sl)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [usr_avp.c:646]:
DEBUG:destroy_avp_list: destroying list (nil)
Such messages periodically sends kamailio. Why kamailio every time
sends yourself these NOTIFY messages, what it try to do ?
I see problem something around auth_db autorization and HA1, isn't it
? How to fix it ?
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
6:12 p.m.
New subject: kamailio realtime integration
Yes, NOTIFY was generated by ipphone.
Thx, again :)
On 06/24/2011 12:00 PM, Daniel-Constantin Mierla wrote:
Hello,
based on the logs, the authentication fails due to wrong password.
Check that you have the right password on client side.
Kamailio does not generate any NOTIFY unless the presence server
modules are loaded. If not, then the notify comes from somewhere else
and it is just looped back due to config file routing logic.
Cheers,
Daniel
On 6/24/11 10:01 AM, vaad.fabi(a)gmail.com wrote:
--
vad fabi
Hi all,
Still trying to run kamailio 3.1.x + asterisk 1.6.2.X realtime
architecture.
As i mentioned earlier, instead of asterisk i use another softswitch
with db, table "retailroute" with "login" and "password"
fields as
user auth data.
Of course, troubles... user can't register to kamailio :(
Logs( without users attempts to register, only kamailio internal logic:
Jun 24 11:23:26 sbc kamailio[17768]: INFO: <script>:
------------------ SIP Request: method [NOTIFY] from
[sip:100@100.100.100.100] to [sip:100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:167]: get_hdr_field: cseq <CSeq>: <811> <NOTIFY>
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: maxfwd [mf_funcs.c:85]:
value = 70
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:201]: DEBUG: get_hdr_body : content_length=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:103]: found end of header
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: siputils [checks.c:73]:
no totag
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1081]:
DEBUG: t_check_msg: msg id=39 global id=38 T start=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:528]:
t_lookup_request: start searching: hash=31430, isACK=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:485]:
DEBUG: RFC3261 transaction matching failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:711]:
DEBUG: t_lookup_request: no transaction found
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1150]:
DEBUG: t_check_msg: msg id=39 global id=39 T end=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [select.c:424]:
Calling SELECT 0x832b7e4
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:501]: grep_sock_info - checking if host==us: 13==13
&& [100.100.100.100] == [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:504]: grep_sock_info - checking if port 5060 matches
port 5060
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db
[authorize.c:239]: realm value [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:95]: auth:
digest-algo: MD5 parsed value: 1
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:118]:
allocate 28 bytes for result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:68]: 1
columns returned from the query
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:155]:
allocate 4 bytes for result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:165]:
allocate 4 bytes for result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:85]:
allocate 8 bytes for RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:92]:
RES_NAMES(0x832c950)[0]=[password]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:136]:
use DB1_STRING result type
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:184]:
allocate 8 bytes for rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:119]:
allocate 20 bytes for row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_val.c:117]:
converting STRING [dav0011]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db
[authorize.c:120]: HA1 string calculated:
a8fdf502e497ff8e9407ac2dc31540df
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:205]:
check_response: Our result = 'fa83bf7c0a7af33cc500aa2b62758931'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:215]:
check_response: Authorization failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:81]:
freeing 1 columns
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:85]:
freeing RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:94]:
freeing result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:99]:
freeing result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:54]:
freeing 1 rows
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:97]:
freeing row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:62]:
freeing rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:136]:
freeing result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:102]:
build_challenge_hf: realm='100.100.100.100'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:236]:
auth: 'Proxy-Authenticate: Digest realm="100.100.100.100",
nonce="TgQ8mU4EO22Odd1W63tOO27IRrKX0kU '
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: sl [sl.c:278]: reply in
stateless mode (sl)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [usr_avp.c:646]:
DEBUG:destroy_avp_list: destroying list (nil)
Such messages periodically sends kamailio. Why kamailio every time
sends yourself these NOTIFY messages, what it try to do ?
I see problem something around auth_db autorization and HA1, isn't it
? How to fix it ?
27 Jun
27 Jun
7:50 a.m.
New subject: kamailio realtime integration
Hi All and Daniel,
My interesting "realtime" story still continues :)
All configuration seems to be ok. It's default but some DB fields
changes as Daniel advised.
Terminals registrations to kamailio is ok (but kamailio don't register
as a endpoint on remote softswitch, but calls run :) is it ok? )
Situation: one logic + two different terminals = two different results
!!! Kamailio logic haven't changes (exclude DB fields) and it's not a
softswitch part.
Is it something around two different requests with
Proxy-Authenticate/realm (one case 193.58.XXX.XXX, second case
VoipSwitch) and why kamailio generates two different realms ?
First case (ok).
Sip terminal - softphone twinkle
Dump from kamailio:
terminal->kamailio
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKeweuqqbi
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
+ SDP
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKeweuqqbi;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.b6c5
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKeweuqqbi
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.b6c5
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 ACK
User-Agent: Twinkle/1.4.2
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKtepuspep
Max-Forwards: 70
Proxy-Authorization: Digest
username="200",realm="193.58.XXX.XXX",nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ",uri="sip:9991@193.58.XXX.XXX",response="e584c40d869c851f631c74c2a874cc02",algorithm=MD5
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
Content-Length: 311
+SDP
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKtepuspep;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
SIP/2.0 407 Proxy Authentication Required
CSeq: 118 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKtepuspep
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050709100033375
Proxy-Authenticate: DIGEST realm="VoipSwitch",
nonce="05f6635f0e211fb3-24050517506070925525"
Content-Length: 0
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKtepuspep
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=050709100033375
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 ACK
User-Agent: Twinkle/1.4.2
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKjgqxpmir
Max-Forwards: 70
Proxy-Authorization: Digest
username="200",realm="193.58.XXX.XXX",nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ",uri="sip:9991@193.58.XXX.XXX",response="e584c40d869c851f631c74c2a874cc02",algorithm=MD5
Proxy-Authorization: Digest
username="200",realm="VoipSwitch",nonce="05f6635f0e211fb3-24050517506070925525",uri="sip:9991@193.58.XXX.XXX",response="c28d02e014adc119f75a839a7ebfb171",algorithm=MD5
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 119 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
Content-Length: 311
+SDP
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKjgqxpmir;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 119 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
IP/2.0 183 Session Progress
CSeq: 119 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKjgqxpmir
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Content-Type: application/sdp
Content-Length: 226
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
+SDP
SIP/2.0 200 OK
CSeq: 119 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKjgqxpmir
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Contact: <sip:93.116.XXX.XXX:5060;transport=udp>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, INFO, NOTIFY,
MESSAGE, SUBSCRIBE, REFER
Content-Type: application/sdp
Content-Length: 226
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
RTP SESSION
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-e8dcc9b4;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=b569480918f4e690o0
To: <sip:193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.f963
Call-ID: 2c9f671d-2c05328c(a)192.168.0.180
CSeq: 473 NOTIFY
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
RTP SESSION
BYE sip:93.116.XXX.XXX:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKepxrurdf
Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 120 BYE
User-Agent: Twinkle/1.4.2
Content-Length: 0
SIP/2.0 200 OK
CSeq: 120 BYE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKepxrurdf
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Content-Length: 0
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
Second case (not ok).
Sip terminal - cisco iphone
Dump from kamailio:
terminal->kamailio
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-1050babb;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 ACK
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-beb5344f;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
SIP/2.0 407 Proxy Authentication Required
CSeq: 102 INVITE
Via: SIP/2.0/UDP
192.168.0.180:5060;rport=5060;received=93.116.XXX.XXX;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Proxy-Authenticate: DIGEST realm="VoipSwitch",
nonce="05f481310df9ef29-24050517506050625525"
Content-Length: 0
Record-Route:
<sip:193.58.XXX.XXX;lr=on;ftag=dfe3d8151250ffabo0;nat=yes>
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-303c9613;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
On 06/24/2011 09:12 PM, vaad.fabi(a)gmail.com wrote:
Yes, NOTIFY was generated by ipphone.
Thx, again :)
On 06/24/2011 12:00 PM, Daniel-Constantin Mierla wrote:
--
Vadim F.
Hello,
based on the logs, the authentication fails due to wrong password.
Check that you have the right password on client side.
Kamailio does not generate any NOTIFY unless the presence server
modules are loaded. If not, then the notify comes from somewhere else
and it is just looped back due to config file routing logic.
Cheers,
Daniel
On 6/24/11 10:01 AM, vaad.fabi(a)gmail.com wrote:
Hi all,
Still trying to run kamailio 3.1.x + asterisk 1.6.2.X realtime
architecture.
As i mentioned earlier, instead of asterisk i use another softswitch
with db, table "retailroute" with "login" and "password"
fields as
user auth data.
Of course, troubles... user can't register to kamailio :(
Logs( without users attempts to register, only kamailio internal logic:
Jun 24 11:23:26 sbc kamailio[17768]: INFO: <script>:
------------------ SIP Request: method [NOTIFY] from
[sip:100@100.100.100.100] to [sip:100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:167]: get_hdr_field: cseq <CSeq>: <811> <NOTIFY>
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: maxfwd [mf_funcs.c:85]:
value = 70
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:201]: DEBUG: get_hdr_body : content_length=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[parser/msg_parser.c:103]: found end of header
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: siputils [checks.c:73]:
no totag
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1081]:
DEBUG: t_check_msg: msg id=39 global id=38 T start=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:528]:
t_lookup_request: start searching: hash=31430, isACK=0
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:485]:
DEBUG: RFC3261 transaction matching failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:711]:
DEBUG: t_lookup_request: no transaction found
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: tm [t_lookup.c:1150]:
DEBUG: t_check_msg: msg id=39 global id=39 T end=(nil)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [select.c:424]:
Calling SELECT 0x832b7e4
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:501]: grep_sock_info - checking if host==us: 13==13
&& [100.100.100.100] == [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[socket_info.c:504]: grep_sock_info - checking if port 5060 matches
port 5060
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db
[authorize.c:239]: realm value [100.100.100.100]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:95]: auth:
digest-algo: MD5 parsed value: 1
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:118]:
allocate 28 bytes for result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:68]:
1 columns returned from the query
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:155]:
allocate 4 bytes for result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:165]:
allocate 4 bytes for result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:85]:
allocate 8 bytes for RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:92]:
RES_NAMES(0x832c950)[0]=[password]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: db_mysql [km_res.c:136]:
use DB1_STRING result type
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:184]:
allocate 8 bytes for rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:119]:
allocate 20 bytes for row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_val.c:117]:
converting STRING [dav0011]
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth_db
[authorize.c:120]: HA1 string calculated:
a8fdf502e497ff8e9407ac2dc31540df
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:205]:
check_response: Our result = 'fa83bf7c0a7af33cc500aa2b62758931'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [api.c:215]:
check_response: Authorization failed
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:81]:
freeing 1 columns
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:85]:
freeing RES_NAMES[0] at 0x832c950
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:94]:
freeing result names at 0x832ba40
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:99]:
freeing result types at 0x832ba08
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:54]:
freeing 1 rows
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_row.c:97]:
freeing row values at 0x832e75c
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:62]:
freeing rows at 0x832c918
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [db_res.c:136]:
freeing result set at 0x832c8cc
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:102]:
build_challenge_hf: realm='100.100.100.100'
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: auth [challenge.c:236]:
auth: 'Proxy-Authenticate: Digest realm="100.100.100.100",
nonce="TgQ8mU4EO22Odd1W63tOO27IRrKX0kU '
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: sl [sl.c:278]: reply in
stateless mode (sl)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core>
[msg_translator.c:204]: check_via_address(XX.116.255.XXX,
192.168.0.180, 0)
Jun 24 11:23:26 sbc kamailio[17768]: DEBUG: <core> [usr_avp.c:646]:
DEBUG:destroy_avp_list: destroying list (nil)
Such messages periodically sends kamailio. Why kamailio every time
sends yourself these NOTIFY messages, what it try to do ?
I see problem something around auth_db autorization and HA1, isn't
it ? How to fix it ?
7:55 a.m.
New subject: kamailio realtime integration
Hi All and Daniel,
My interesting "realtime" story still continues :)
All configuration seems to be ok. It's default but some DB fields
changes as Daniel advised.
Terminals registrations to kamailio is ok (but kamailio don't register
as a endpoint on remote softswitch, but calls run :) is it ok? )
Situation: one logic + two different terminals = two different results
!!! Kamailio logic haven't changes (exclude DB fields) and it's not a
softswitch part.
Is it something around two different requests with
Proxy-Authenticate/realm (one case 193.58.XXX.XXX, second case
VoipSwitch) and why kamailio generates two different realms ?
First case (ok).
Sip terminal - softphone twinkle
Dump from kamailio:
terminal->kamailio
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKeweuqqbi
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
+ SDP
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKeweuqqbi;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.b6c5
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKeweuqqbi
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.b6c5
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 117 ACK
User-Agent: Twinkle/1.4.2
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKtepuspep
Max-Forwards: 70
Proxy-Authorization: Digest
username="200",realm="193.58.XXX.XXX",nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ",uri="sip:9991@193.58.XXX.XXX",response="e584c40d869c851f631c74c2a874cc02",algorithm=MD5
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
Content-Length: 311
+SDP
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKtepuspep;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
SIP/2.0 407 Proxy Authentication Required
CSeq: 118 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKtepuspep
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050709100033375
Proxy-Authenticate: DIGEST realm="VoipSwitch",
nonce="05f6635f0e211fb3-24050517506070925525"
Content-Length: 0
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKtepuspep
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=050709100033375
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 118 ACK
User-Agent: Twinkle/1.4.2
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKjgqxpmir
Max-Forwards: 70
Proxy-Authorization: Digest
username="200",realm="193.58.XXX.XXX",nonce="TgR+704EfcMLI76IHmIgL4DU9ED7DulQ",uri="sip:9991@193.58.XXX.XXX",response="e584c40d869c851f631c74c2a874cc02",algorithm=MD5
Proxy-Authorization: Digest
username="200",realm="VoipSwitch",nonce="05f6635f0e211fb3-24050517506070925525",uri="sip:9991@193.58.XXX.XXX",response="c28d02e014adc119f75a839a7ebfb171",algorithm=MD5
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 119 INVITE
Contact: <sip:200@192.168.0.174:5065>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
Content-Length: 311
+SDP
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.174:5065;rport=5065;branch=z9hG4bKjgqxpmir;received=93.116.XXX.XXX
To: <sip:9991@193.58.XXX.XXX>
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 119 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
IP/2.0 183 Session Progress
CSeq: 119 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKjgqxpmir
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Content-Type: application/sdp
Content-Length: 226
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
+SDP
SIP/2.0 200 OK
CSeq: 119 INVITE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKjgqxpmir
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Contact: <sip:93.116.XXX.XXX:5060;transport=udp>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, INFO, NOTIFY,
MESSAGE, SUBSCRIBE, REFER
Content-Type: application/sdp
Content-Length: 226
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
RTP SESSION
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-e8dcc9b4;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=b569480918f4e690o0
To: <sip:193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.f963
Call-ID: 2c9f671d-2c05328c(a)192.168.0.180
CSeq: 473 NOTIFY
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
RTP SESSION
BYE sip:93.116.XXX.XXX:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.0.174:5065;rport;branch=z9hG4bKepxrurdf
Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
Max-Forwards: 70
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
CSeq: 120 BYE
User-Agent: Twinkle/1.4.2
Content-Length: 0
SIP/2.0 200 OK
CSeq: 120 BYE
Via: SIP/2.0/UDP
192.168.0.174:5065;received=93.116.XXX.XXX;rport=5065;branch=z9hG4bKepxrurdf
From: "kamailio" <sip:200@193.58.XXX.XXX>;tag=wvgqh
Call-ID: lutmonzrdvxboxk@SipuraSPA
To: <sip:9991@193.58.XXX.XXX>;tag=050710100033890
Content-Length: 0
Record-Route: <sip:193.58.XXX.XXX;lr=on;ftag=wvgqh;nat=yes>
Second case (not ok).
Sip terminal - cisco iphone
Dump from kamailio:
terminal->kamailio
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-1050babb;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 ACK
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-beb5344f;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
SIP/2.0 407 Proxy Authentication Required
CSeq: 102 INVITE
Via: SIP/2.0/UDP
192.168.0.180:5060;rport=5060;received=93.116.XXX.XXX;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Proxy-Authenticate: DIGEST realm="VoipSwitch",
nonce="05f481310df9ef29-24050517506050625525"
Content-Length: 0
Record-Route:
<sip:193.58.XXX.XXX;lr=on;ftag=dfe3d8151250ffabo0;nat=yes>
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-303c9613;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
8:03 a.m.
New subject: kamailio realtime integration
Hi All and Daniel,
My interesting "realtime" story still continues :)
All configuration seems to be ok. It's default but some DB fields
changes as Daniel advised.
Terminals registrations to kamailio is ok (but kamailio don't register
as a endpoint on remote softswitch, but calls run :) is it ok? )
Situation: one logic + two different terminals = two different results
!!! Kamailio logic haven't changes (exclude DB fields) and it's not a
softswitch part.
Is it something around two different requests with
Proxy-Authenticate/realm (one case 193.58.XXX.XXX, second case
VoipSwitch) and why kamailio generates two different realms ?
First case (ok).
Sip terminal - softphone twinkle
Dump from kamailio:
http://pastebin.com/uddxwf6F
Second case (not ok).
Sip terminal - cisco iphone
Dump from kamailio:
terminal->kamailio
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-1050babb;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-1050babb
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.9e28
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 101 ACK
Max-Forwards: 70
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-beb5344f;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 INVITE
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
SIP/2.0 407 Proxy Authentication Required
CSeq: 102 INVITE
Via: SIP/2.0/UDP
192.168.0.180:5060;rport=5060;received=93.116.XXX.XXX;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Proxy-Authenticate: DIGEST realm="VoipSwitch",
nonce="05f481310df9ef29-24050517506050625525"
Content-Length: 0
Record-Route:
<sip:193.58.XXX.XXX;lr=on;ftag=dfe3d8151250ffabo0;nat=yes>
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-beb5344f
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=05050699909937
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 102 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="193.58.XXX.XXX",nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="69dcc7441ad6f0a70c259e8948d8fcf0"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
INVITE sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
Expires: 240
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 259
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
kamailio->terminal
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.180:5060;branch=z9hG4bK-303c9613;rport=5060;received=93.116.XXX.XXX
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 INVITE
Proxy-Authenticate: Digest realm="193.58.XXX.XXX",
nonce="TgR+dE4EfUj/W4ocJ0iFmM93MMo5SgvE"
Server: kamailio (3.1.4 (i386/linux))
Content-Length: 0
terminal->kamailio
ACK sip:9991@193.58.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 192.168.0.180:5060;branch=z9hG4bK-303c9613
From: "100" <sip:100@193.58.XXX.XXX>;tag=dfe3d8151250ffabo0
To: <sip:9991@193.58.XXX.XXX>;tag=636f77b6676bf8d50aad9baa13cd3627.4a95
Call-ID: 8760c7dd-41ef9283(a)192.168.0.180
CSeq: 103 ACK
Max-Forwards: 70
Proxy-Authorization: Digest
username="100",realm="VoipSwitch",nonce="05f481310df9ef29-24050517506050625525",uri="sip:9991@193.58.XXX.XXX",algorithm=MD5,response="70b633a0ca9ecf0bfebb7792f843d732"
Contact: "100" <sip:100@192.168.0.180:5060>
User-Agent: Linksys/SPA922-5.1.15(a)
Content-Length: 0
--
Vadim F.
4705
days inactive
4712
days old
12 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Meftah Tayeb -
vaad.fabi＠gmail.com