Pjsip.endpoint_custom_post.conf doesn't get applied if a trunk is disabled

I’m using pjsip.endpoint_custom_post.conf like this, and it works 100% perfect as long as both trunks are enabled.

[Trunk1](+)
transport=transport-Trunk1

[Trunk2](+)
transport=transport-Trunk2

However, if I disable Trunk1, this file stops working. Trunk2 goes back to the default transport of 0.0.0.0-udp because the settings in this file are not applied. I’m sure this is because Trunk1 missing is causing the processing engine to error out and stop processing custom files.

Is there anyway that I can fix this so that if I were to disable either trunk (for whatever reason), the custom file would continue to work for the remaining entries?

No, not as far as I know. What I do is this:

Whenever I disable/enable a trunk, I comment/uncomment the section for that trunk in pjsip.endpoint_custom_post.conf, followed by the command ‘fwconsole reload’.

Yes, this is a minor nuisance.

If someone does have a solution for this I too would like to know.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.