It happened again!

VitalPBX Community Support General Discussion It happened again!

  • Post
    jrosetto
    Participant

    So I am modifying settings in the VitalPBX gui and all of a sudden Tenant 2’s phones are not registering.  I Look in the GUI and all the configuration looks fine.  Going to asterisk and running ‘pjsip show endpoints’ and all endpoints for Tenant 2 are missing.  Tried rebooting, restarting asterisk, resubmitting from the GUI but nothing seems to bring them back.

    Here are the errors in asterisk

    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf=
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf
    [2020-03-11 10:48:49] WARNING[5588]: config.c:1816 process_text_line: Inheritance requested, but category ‘p12’ does not exist, line 597 of /etc/asterisk/ombutel/pjsip__50-1-trunks.conf

    Again I am reluctant to put a bunch of tenants on this platform if it is going to keep giving me issues.  It seems like if I don’t touch anything it works great but the second I start doing modifications in the GUI to enhance things it begins to break.  This time I went for about 5 days without issues doing modifications then all of a sudden I am back in the same boat.

    Help or suggestions are greatly appreciated,

    Thanks.

    0
Viewing 6 replies - 1 through 6 (of 6 total)
  • Replies
    Up
    0
    Down

    Looks like you remove the PJSIP profile assigned to your trunks in the main tenant.

    0
    jrosetto
    Participant
    Up
    0
    Down

    @ing-joserivera26

    I absolutely did because I was having issues with TLS.  Why does this affect my additional tenants?

     

    0
    Up
    0
    Down

    Because the profiles are assigned to the devices and the trunks, so, if the profile doesn’t exist then, the devices are not generated by asterisk.

    0
    jrosetto
    Participant
    Up
    0
    Down

    @ing-joserivera26

    I had one trunk under the main tenant the profile was assigned to which was called PJSIP TLS Profile.  The trunk and extensions on the secondary tenant were all set to Default PJSIP Profile which was never touched.  Still confused as to why I didn’t take down the main tenant but somehow managed to take down the secondary tenant.

     

    0
    jrosetto
    Participant
    Up
    0
    Down

    @ing-joserivera26

    I guess the reason is moot at this point.  My original issue was that I can’t get TLSv3 to listen on port 5063.  I tried to delete the profile to recreate it and ran into the other issues.  I restored from backup to get back up and running.  Here are the errors I am getting

    [2020-03-11 11:31:51] ERROR[24094]: config_options.c:798 aco_process_var: Error parsing method=tlsv3 at line 49 of /etc/asterisk/ombutel/pjsip__20-transport.conf
    [2020-03-11 11:31:51] ERROR[24094]: res_sorcery_config.c:407 sorcery_config_internal_load: Could not create an object of type ‘transport’ with id ‘transport-tls’ from configuration file ‘pjsip.conf’

    I am using a LetEncrypt Certificate, have a TLS profile created, and SSL Method set to TLSv3 in PJSIP Settings.  I also have the extension set to use the TLS profile.  What am I missing here?

     

    0
    Up
    0
    Down

    PJSIP methods:

    • default – The default as defined by PJSIP. This is currently TLSv1, but may change with future releases.
    • unspecified – This option is equivalent to setting ‘default’
    • tlsv1
    • tlsv1_1
    • tlsv1_2
    • sslv2
    • sslv3
    • sslv23
    0
Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.