| Summary: | ASTERISK-01231: md5/secret not possible with Draytek 2600V: chan_sip.c | ||
| Reporter: | chrisorme (chrisorme) | Labels: | |
| Date Opened: | 2004-03-17 08:18:13.000-0600 | Date Closed: | 2004-09-25 02:53:52 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | * does not recognise the (authentication?) format provided by the Draytek 2600V when it provides a secret. The Draytek 2600V registers fine without a secret. ****** ADDITIONAL INFORMATION ****** Is there an easy way to dump the sip debug to a file in chan_sip.c so I could see where in (auth_user ??) this is going wrong and maybe I or someone or attempt to rewrite this bit of code (that doesn't look very nice and I'm not a programmer)? Maybe this is a debugging feature that could be put in via a variable at the top. The Draytek registration doesn't fail under LAN traffic like my previous bug report as no secret can be used. | ||
| Comments: | By: zoa (zoa) 2004-03-17 08:24:03.000-0600 use putty... and log it to file with asterisk -r By: Brian West (bkw918) 2004-03-17 21:32:42.000-0600 sip debug then post the transaction as with your other bug also. By: chrisorme (chrisorme) 2004-03-17 22:04:20.000-0600 I just tried to reproduce this bug with the very latest CVS and md5 authentication worked between the Draytek and *. (this is with the CVS as is without my nasty return 0; hack placed at the start of auth_user(?) in chan_sip.c as mentioned in the LAN traffic pushing over authentication bug I posted - It's probably best to close this bug for now and if I can duplicate this bug again it again I'll reopen this. But I think it must have got fixed along the way - Thanks for being patient with me. Chris | ||