ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Yealink will not register with VitalPBX, Wrong password

    IT Discussion
    vitalpbx
    3
    18
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JasGot
      last edited by

      If I have verified the correct password, what could be causing:
      [2019-07-12 10:18:41] NOTICE[1826] chan_sip.c: Registration from '"JasGot" sip:[email protected]:5060' failed for '192.168.100.21:5060' - Wrong password

      JaredBuschJ 1 Reply Last reply Reply Quote 1
      • RomoR
        Romo
        last edited by

        @JasGot Are you using the autogenerated password? Have you tried setting a different one and using that?

        Also worth checking is the device for the extension set as SIP and not PJSIP?

        J 1 Reply Last reply Reply Quote 1
        • JaredBuschJ
          JaredBusch @JasGot
          last edited by

          @JasGot said in Yealink will not register with VitalPBX, Wrong password:

          [2019-07-12 10:18:41] NOTICE[1826] chan_sip.c: Registration from '"JasGot" sip:[email protected]:5060' failed for '192.168.100.21:5060' - Wrong password

          Your extension is "jasgot" that is abnormal. How are people supposed to dial that?

          RomoR J 2 Replies Last reply Reply Quote 0
          • RomoR
            Romo @JaredBusch
            last edited by

            @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

            JaredBuschJ 2 Replies Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @Romo
              last edited by

              @Romo said in Yealink will not register with VitalPBX, Wrong password:

              @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

              I know it is possible. I said it is abnormal. I should have clarified my response. That is my bad.

              J 1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch
                last edited by

                What tech is your extension using? and then how did you configure the tech in the PBX settings?

                18f55c97-1c82-4ad4-a317-b45a31e30d46-image.png

                If your password was auto-generated with special characters remove them.
                0285b63a-85f2-43b1-bddf-3bf7effc6b0f-image.png

                1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch
                  last edited by

                  VitalPBX is bad in that they are still pushing SIP as the primary technology on port 5060.
                  b86bc545-e279-446b-ae94-ad381f64cbac-image.png

                  PJSIP is on 5062.
                  f76c726b-307a-4c26-9843-945217b5a2a7-image.png

                  Asterisk has depreciated SIP in favor of PJSIP since Asterisk 13. Yet VitalPBX promotes that they are using Asterisk 16.4. To me, these two things work hard against each other.

                  J 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @Romo
                    last edited by JaredBusch

                    @Romo said in Yealink will not register with VitalPBX, Wrong password:

                    @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

                    The better question is why are you even thinking this is a good idea?

                    What benefit are you thinking you are gaining by using a non-standard approach?

                    All this does is complicate things by putting a random value in a place that is normally something that matches the extension. This is a 1 to 1 tie between this informaiton and the extension. There is no benefit to this.

                    RomoR J 2 Replies Last reply Reply Quote 0
                    • RomoR
                      Romo @JaredBusch
                      last edited by

                      @JaredBusch Quoted the wrong post?

                      I didn't express an opinion regarding if this was good or not, just said Vital allowed it =).

                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch @Romo
                        last edited by

                        @Romo said in Yealink will not register with VitalPBX, Wrong password:

                        @JaredBusch Quoted the wrong post?

                        I didn't express an opinion regarding if this was good or not, just said Vital allowed it =).

                        Just a thought to ask the question as to why you were doing it. any one post would be as good as another to quote..

                        So why are you doing it?

                        1 Reply Last reply Reply Quote 0
                        • RomoR
                          Romo
                          last edited by

                          I am not doing it 😃 , I am not the OP.

                          JaredBuschJ 1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch @Romo
                            last edited by

                            @Romo said in Yealink will not register with VitalPBX, Wrong password:

                            I am not doing it 😃 , I am not the OP.

                            I apparently need a damned nap...

                            1 Reply Last reply Reply Quote 1
                            • J
                              JasGot @Romo
                              last edited by

                              @Romo Had to do SIP on the device, rather than PJSIP. Thanks. This was it.

                              1 Reply Last reply Reply Quote 0
                              • J
                                JasGot @JaredBusch
                                last edited by

                                @JaredBusch What does that have to do with password authentication?

                                1 Reply Last reply Reply Quote 0
                                • J
                                  JasGot @JaredBusch
                                  last edited by

                                  @JaredBusch said in Yealink will not register with VitalPBX, Wrong password:

                                  @Romo said in Yealink will not register with VitalPBX, Wrong password:

                                  @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

                                  I know it is possible. I said it is abnormal. I should have clarified my response. That is my bad.

                                  Yes it is.

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    JasGot @JaredBusch
                                    last edited by

                                    @JaredBusch said in Yealink will not register with VitalPBX, Wrong password:

                                    @Romo said in Yealink will not register with VitalPBX, Wrong password:

                                    @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

                                    The better question is why are you even thinking this is a good idea?

                                    What benefit are you thinking you are gaining by using a non-standard approach?

                                    All this does is complicate things by putting a random value in a place that is normally something that matches the extension. This is a 1 to 1 tie between this informaiton and the extension. There is no benefit to this.

                                    Only after you've pigeon-holed yourself into that 1 to 1 relationship.

                                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                                    • J
                                      JasGot @JaredBusch
                                      last edited by

                                      @JaredBusch said in Yealink will not register with VitalPBX, Wrong password:

                                      VitalPBX is bad in that they are still pushing SIP as the primary technology on port 5060.
                                      b86bc545-e279-446b-ae94-ad381f64cbac-image.png

                                      PJSIP is on 5062.
                                      f76c726b-307a-4c26-9843-945217b5a2a7-image.png

                                      Asterisk has depreciated SIP in favor of PJSIP since Asterisk 13. Yet VitalPBX promotes that they are using Asterisk 16.4. To me, these two things work hard against each other.

                                      I will circle back and try PJSIP again with the corrected ports. I would prefer PJSIP.

                                      1 Reply Last reply Reply Quote 0
                                      • JaredBuschJ
                                        JaredBusch @JasGot
                                        last edited by

                                        @JasGot said in Yealink will not register with VitalPBX, Wrong password:

                                        @JaredBusch said in Yealink will not register with VitalPBX, Wrong password:

                                        @Romo said in Yealink will not register with VitalPBX, Wrong password:

                                        @JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

                                        The better question is why are you even thinking this is a good idea?

                                        What benefit are you thinking you are gaining by using a non-standard approach?

                                        All this does is complicate things by putting a random value in a place that is normally something that matches the extension. This is a 1 to 1 tie between this informaiton and the extension. There is no benefit to this.

                                        Only after you've pigeon-holed yourself into that 1 to 1 relationship.

                                        No, it is a 1 to 1 relationship regardless of if you use the extension or a name or a fuck01.

                                        That auth name is 100% tied 1 to 1 to the extension.

                                        1 Reply Last reply Reply Quote 0
                                        • 1 / 1
                                        • First post
                                          Last post