Hi,
I am using UAC to register to an outbound provider. Kamailio (3.1.0) does send the following REGISTER:
E..'A...@.=...P...P9......\1REGISTER sip:172.16.0.57 SIP/2.0
Via: SIP/2.0/UDP 172.16.0.130;branch=z9hG4bKa69c.50411006.0
To: sip:SIP001@172.16.0.57
From: sip:SIP001@172.16.0.57;tag=533cb9e91f4b999cf76861cbb9ed54ed-c10d
CSeq: 10 REGISTER
Call-ID: 7bad8cfd-13535(a)127.0.0.1
Content-Length: 0
User-Agent: kamailio (3.1.0 (i386/linux))
Contact: <sip:@172.16.0.130>
Expires: 600
Authorization: Digest username="SIP001", realm="asterisk", nonce="1be9f4f2", uri="sip:172.16.0.57", response="e46d865eb495e170fdef058b857d7b76", algorithm=MD5
I am not really 100% sure, but I think the Contact address is not valid. Within the database I have only set the host part. I think the Contact should be the following then:
Contact: <sip:172.16.0.130)
(without the @).
In addition, I think the Call-ID could be better. I know, that it is valid to set it like that, but the IP Address 127.0.0.1 could be misunderstood somewhere.
Best regards,
Bernhard Suttner
Module: sip-router
Branch: master
Commit: 0f5e21c668e46492fb9f9ec69e5b5aafe41bd272
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0f5e21c…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Fri Dec 3 10:45:00 2010 +0100
dispatcher(k): fixed use of use_default parameter
- when there was a single destination in destination set and it was in
inactive state, then having parameter use_default=1 caused a divion by
0 while atteptimpting to look for active destaintaion
- reported by Eric Hiller
---
modules_k/dispatcher/dispatch.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/modules_k/dispatcher/dispatch.c b/modules_k/dispatcher/dispatch.c
index bcd7f7c..e42f5d8 100644
--- a/modules_k/dispatcher/dispatch.c
+++ b/modules_k/dispatcher/dispatch.c
@@ -1717,15 +1717,20 @@ int ds_select_dst(struct sip_msg *msg, int set, int alg, int mode)
while ((idx->dlist[i].flags & DS_INACTIVE_DST)
|| (idx->dlist[i].flags & DS_PROBING_DST))
{
- if(ds_use_default!=0)
+ if(ds_use_default!=0 && idx->nr!=1)
i = (i+1)%(idx->nr-1);
else
i = (i+1)%idx->nr;
if(i==hash)
{
+ /* back to start -- looks like no active dst */
if(ds_use_default!=0)
{
i = idx->nr-1;
+ if((idx->dlist[i].flags & DS_INACTIVE_DST)
+ || (idx->dlist[i].flags & DS_PROBING_DST))
+ return -1;
+ break;
} else {
return -1;
}
@@ -1751,6 +1756,7 @@ int ds_select_dst(struct sip_msg *msg, int set, int alg, int mode)
if(dst_avp_name.n!=0)
{
+ /* add default dst to last position in AVP list */
if(ds_use_default!=0 && hash!=idx->nr-1)
{
avp_val.s = idx->dlist[idx->nr-1].uri;
Hi,
first of all - thanks to all these great modules, the kamailio core, the very well documented features. This project is really very well maintained.
I am using the UAC module (V 3.1.0) to make an outbound registration. During testing I used the wrong "realm" for the registration. The result within the log was thousands line of:
...
41(13280) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
44(13286) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
46(13290) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
42(13282) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
44(13286) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
43(13284) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
47(13292) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
45(13288) ERROR: uac [uac_reg.c:505]: realms are different - ignire?!?!
...
And a REGISTER flood from Kamailio to the registration endpoint.
After that, I recognized that I have to restart kamailio to fix the realm. It would be cool to have a "kamctl" function to reload this module.
Best regards and have a nice weekend.
Bernhard Suttner
Hello,
Kamailio SIP Server v3.1.1 is released.
This is a maintenance release of latest stable branch, 3.1, that
includes fixes since release of v3.1.0. There is no change to database
or configuration file required to upgrade to 3.1.1 from 3.1.0 version.
If you run v3.1.0 from tarball or packages, it is strongly recommended
to upgrade to v3.1.1.
For more details about version 3.1.1, visit:
http://www.kamailio.org/w/2010/12/kamailio-v3-1-1-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com