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.
PJSIP is on 5062.
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.
-
@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.
-
@JaredBusch Quoted the wrong post?
I didn't express an opinion regarding if this was good or not, just said Vital allowed it =).
-
@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?
-
I am not doing it
, I am not the OP. -
@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...
-
@Romo Had to do SIP on the device, rather than PJSIP. Thanks. This was it.
-
@JaredBusch What does that have to do with password authentication?
-
@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.
-
@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.
-
@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.
PJSIP is on 5062.
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.
-
@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.
