[asterisk-bugs] [JIRA] (ASTERISK-22438) Asterisk 1.8.23.0 - Loop Registration

Rusty Newton (JIRA) noreply at issues.asterisk.org
Thu Sep 5 19:15:03 CDT 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209996#comment-209996 ] 

Rusty Newton commented on ASTERISK-22438:
-----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks!


                
> Asterisk 1.8.23.0 - Loop Registration
> -------------------------------------
>
>                 Key: ASTERISK-22438
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22438
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>            Reporter: Sylvio Jollenbeck
>
> Hello Guys
>      I'm using Asterisk 1.8.23, in my sip.conf MAX-Forwards this set to 70, but this limit is not being respected.
>     Another point are the messages: Correct auth, but based on stale nonce received from. In my sip.conf pedantic = no.
> Cli:
> <--- SIP read from UDP:10.80.2.159:5060 --->
> REGISTER sip:10.90.0.211:5060 SIP/2.0
> Via: SIP/2.0/UDP 10.80.2.159:5060;branch=z9hG4bK17876b539d7f115224e304;rport
> From: "20041" <sip:20041 at 10.90.0.211:5060>;tag=17876bd2ae
> To: "20041" <sip:20041 at 10.90.0.211:5060>
> Call-ID: 6ad01c-17ea1-5224e2e2 at 10.90.0.211
> CSeq: 1787 REGISTER
> Contact: "20041" <sip:20041 at 10.80.2.159:5060>
> Authorization: Digest username="20041", realm="HT", nonce="5dfef0cf", uri="sip:10.90.0.211", response="5280dcd048df95b194fdffeef995fd02", algorithm=MD5
> User-Agent: VaxSIPUserAgent/3.1
> Expires: 3600
> Max-Forwards: 70
> Content-Length: 0
> <------------->
> --- (12 headers 0 lines) ---
> Sending to 10.80.2.159:5060 (no NAT)
> [Sep  2 16:09:58] NOTICE[29822]: chan_sip.c:15065 check_auth: Correct auth, but based on stale nonce received from '"20041" <sip:20041 at 10.90.0.211:5060>;tag=17876bd2ae'
> <--- Transmitting (no NAT) to 10.80.2.159:5060 --->
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 10.80.2.159:5060;branch=z9hG4bK17876b539d7f115224e304;received=10.80.2.159;rport=5060
> From: "20041" <sip:20041 at 10.90.0.211:5060>;tag=17876bd2ae
> To: "20041" <sip:20041 at 10.90.0.211:5060>;tag=as7c9fcae4
> Call-ID: 6ad01c-17ea1-5224e2e2 at 10.90.0.211
> CSeq: 1787 REGISTER
> Server: HT AIO
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
> Supported: replaces, timer
> WWW-Authenticate: Digest algorithm=MD5, realm="HT", nonce="753ab0ab", stale=true
> Content-Length: 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list