[arm-allstar] Trouble with iaxrpt

[pjg]

Doug,

Thanks for the info, I have been looking for that answer about the diff 
between the types.

I spent hours trying to figure out what was wrong, I shortened the 
iax.conf to only general and iaxrpt sections and then tried every option 
I could find listed but could not get type=user to work.  I was not sure 
that "friend" was as secure as "user".

Thanks again for the great work!!!!
Paul

On 4/20/2017 12:49 AM, "Doug Crompton via arm-allstar" wrote:
> Paul,
>
> I am not sure why 'user' would not work since this is strictly and incoming
> call but if 'friend' works then go with it. It is a little confusing at
> times but I suspect it is an authorization problem. Here is a definition of
> the type's -
>
>       type = [user|peer|friend]: This line tells Asterisk how to interpret
> this entity. Users are things
> that connect to us, while peers are people we connect to, and a friend is
> shorthand for creating a user and a peer with identical information.
>
> The case of incoming calls from the peer, the IP address must match in
> order for the invitation to work. This means calls made from either
> direction won't work if the peer is unregistered while host=dynamic or if
> the host is otherwise not set to the correct IP of the sender.
>
> For entities with 'type=user': Asterisk users handle inbound calls only
> (meaning they call Asterisk, Asterisk can't ; call them) and are matched by
> their authorization information (authname and secret). Asterisk doesn't
> rely on their IP and will accept calls regardless of the host setting as
> long as the incoming invite authorizes successfully.
>
> For entities with 'type=friend': Asterisk will create the entity as both a
> friend and a peer. Asterisk will accept calls from friends like it would
> for users, requiring only that the authorization matches rather than the IP
> address. Since it is also a peer, a friend entity can be called as long as
> its IP is known to Asterisk. In the case of host=dynamic, this means it is
> necessary for the entity to register before Asterisk can call it.
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Apr 19, 2017 at 8:11 PM, "pjg via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Hi,
>>
>> I just did a clean install of the new V1.5rc2 image on a RPI 2. Everything
>> is seams to be working fine. But when I try to connect from my android or
>> PC using iaxrpt I get a message saying:
>>
>> chan_iax2.c:6858 register_verify: No registration for peer 'iaxrpt' (from
>> 192.168.1.167)
>>
>> If I change the type=user to type=friend in iax.conf file, I am able to
>> connect ok.
>>
>> I did a new clean install because I was having the same issue on a
>> previous install but I thought I might have changed something on the last
>> install.
>>
>> Any ideas?
>>
>> Paul
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>