6 Dec
2010
6 Dec
'10
9:09 p.m.
Hello,
interesting, a negative reply (like 401/407) closes the transaction and
the dialog, so a new one has to be generated. I would have to check the
RFC if for registration authentication it requires to preserve the call
id and the From tag from the first REGISTER sent without credentials.
Maybe Inaki (cc-ed) knows by hart and can reply faster here.
You can use our tracker to register your wish list, there is won't get
lost and will be implemented as the time allows.
http://sip-router.org/tracker/
Thanks for troubleshooting.
Cheers,
Daniel
On 12/6/10 7:50 PM, Bernhard Suttner wrote:
Hi
within Asterisk Debug Log I see:
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: Allocating new SIP dialog for
73ffbded-5469(a)127.0.0.1 - REGISTER (No RTP)
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: **** Received REGISTER (2) - Command in SIP
REGISTER
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: = No match Their Call ID:
73ffbded-5469(a)127.0.0.1 Their Tag 533cb9e91f4b999cf76861cbb9ed54ed-a2b5 Our tag:
as623e27a6
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: Allocating new SIP dialog for
73ffbded-5434(a)127.0.0.1 - REGISTER (No RTP)
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: **** Received REGISTER (2) - Command in SIP
REGISTER
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: = No match Their Call ID:
73ffbded-5434(a)127.0.0.1 Their Tag 533cb9e91f4b999cf76861cbb9ed54ed-76c6 Our tag:
as1c8b03db
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: = No match Their Call ID:
73ffbded-5469(a)127.0.0.1 Their Tag 533cb9e91f4b999cf76861cbb9ed54ed-a2b5 Our tag:
as623e27a6
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: Allocating new SIP dialog for
73ffbded-5438(a)127.0.0.1 - REGISTER (No RTP)
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: **** Received REGISTER (2) - Command in SIP
REGISTER
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: = No match Their Call ID:
73ffbded-5438(a)127.0.0.1 Their Tag 533cb9e91f4b999cf76861cbb9ed54ed-89e8 Our tag:
as1d53d607
[Dec 6 13:42:18] DEBUG[3043] chan_sip.c: = No match Their Call ID:
73ffbded-5434(a)127.0.0.1 Their Tag 533cb9e91f4b999cf76861cbb9ed54ed-76c6 Our tag:
as1c8b03db
Within the trace I see, that Asterisk does set the to-tag within the
"unauthorized" towards Kamailio. Kamailio does then send the REGISTER Request
with authentication credentials but _without_ the to-tag.
Best regards,
Bernhard Suttner
----- Original Message -----
From: Bernhard Suttner [mailto:bernhard.suttner@winet.ch]
To: sr-dev(a)lists.sip-router.org
Sent: Mon, 06 Dec 2010 12:07:22 +0100
Subject: [sr-dev] UAC module
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
Hi @ all,
I tried to get the UAC module working on a asterisk but still without luck
and saw some "necessary" improvements for UAC-Reg.
If there is somewhere a "wish-list" I could add that there:
1. if the registration is not successful the first time, Kamailio will never
try it again.
2. if the authentication is not successful, Kamailio will send the
registration for authentication again and again for about 100times a second.
3. UAC-reg "reload" command for kamctl
Best regards,
Bernhard
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev