[Home]

Summary:ASTERISK-01549: possible iax2 authentication regression from stable to head
Reporter:cloos (cloos)Labels:
Date Opened:2004-05-06 16:02:14Date Closed:2011-06-07 14:10:48
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:with originator running head, if gateway runs stable calls via the gateway generate a packet trace like this:

o>g  NEW
<   AUTHREQ
>   AUTHREP
<   ACCEPT
>   ACK
<   Control Actual codec capability
>   ACK
>   HANGUP
<   ACK

but if the gw is running head, there is no AUTHREQ, just
a REJECT.

I am using md5 auth, gw has a type=user block and originator has a type=peer block in iax.conf.
Comments:By: Mark Spencer (markster) 2004-05-06 16:31:56

The behavior of what happens when you receive a call with no specified username has changed.  If you find someone (even me) on IRC we can look and see what is different.

By: cloos (cloos) 2004-05-06 17:04:45

Yes, i just discovered that the laptop's dialplan was to blame....

Instead of -ENOCOFFE I'll blame this oversight on -ETOOMUCHTEA. :-/

At least I was foresighted enough to say *possible* regression.

I don't need the case of no username to work right now (as long as it will Do The Right Thing for eg published enum records), so feel free to close this one out.

So feel free to close this one out.

(It is too bad the reported cannot do that.)