[asterisk-users] pjsip: TOS not working any more

[Michael Maier]

On 08/09/2018 at 10:49 PM Michael Maier wrote:
> Hello!
> 
> I'm using TOS as shown below with pjsip 13.22.0-rc1 (same with 13.21.1).
> Unfortunately, the TOS isn't set in reality any more (it used to work
> some time ago).

Got the problem.

I'm using freepbx and for the configuration of TOS, I'm using the
individual config file pjsip.endpoint_custom_post.conf.

After disabling one of my trunks via GUI, this trunk couldn't be find
any more by asterisk in pjsip.endpoint_custom_post.conf and the complete
configuration provided there was ignored. I had to comment out the
deactivated trunk. Now it's working again.

But I'm wondering why I have to define TOS for each trunk individually
if it is already defined for the transport as defined below?


Thanks,
Michael


> 
> 
> Transport:  <TransportId........>  <Type>  <cos>  <tos>
> <BindAddress....................>
> ==========================================================================================
> 
> 
> Transport:  0.0.0.0-udp               udp      0    184  0.0.0.0:5061
> 
>  ParameterName              : ParameterValue
>  ======================================================
>  allow_reload               : true
>  async_operations           : 1
>  bind                       : 0.0.0.0:5061
>  ca_list_file               :
>  ca_list_path               :
>  cert_file                  :
>  cipher                     :
>  cos                        : 0
>  domain                     :
>  external_media_address     :
>  external_signaling_address :
>  external_signaling_port    : 0
>  local_net                  : 192.168.13.0/255.255.255.0
>  local_net                  : 192.168.17.0/255.255.255.0
>  method                     : unspecified
>  password                   :
>  priv_key_file              :
>  protocol                   : udp
>  require_client_cert        : No
>  symmetric_transport        : false
>  tos                        : 184
>  verify_client              : No
>  verify_server              : No
>  websocket_write_timeout    : 100
>