[asterisk-dev] Configured IPv6 transport in endpoint being overwritten by IPv4

[roger]

On 13/05/2020 17:04, roger wrote:
>
> On 13/05/2020 13:44, roger wrote:
>> I will strip strip everything out of the conf files except the ipv6 
>> stuff and see what happens.
>
> The stripped out version  retains the ipv6 transport. I will do some 
> more testing to try and isol;ate which parts of the old config cause 
> the problem.
>

I have no  pinned the problem.down to two lines in the pjsip endpoint 
config.

[anonymous](+)
transport=ipv6

These date back to when I first did the work to get IPv6 working with 
freepbx. I had to put this in for some reason I no longer remember. The 
anonymous endpoint is now longer created by freepbx. So this config is 
not needed anymore.

However I not determined how these lines interfere with the transport 
setting in the ipv6 endpoint that is created earlier on the config.The 
only thing is see in the log files is are a number of lines like this.

[2020-05-14 12:48:37] WARNING[19078] config.c: Category addition 
requested, but category 'anonymous' does not exist, line 1 of 
/etc/asterisk/pjsip.endpoint_custom_post.conf

So the question is does this warning mean that the rest of the file is 
ignored?

If it does that6 explains the problem I see. But the warning is 
msileading, it should be an error and should tell the user that the rest 
of the file has been ignored.

If I look at the  config on the system I used for the initial (working) 
test these lines are commented out. On the system I am using now they 
are the original old ones which are not.

If the warning does not stop parsing the file then the problem more 
serious and is elsewhere.


Roger

Roger