Nice to know you via e-mail. I meet 1 issue, need your kindly help.
PBX Version is Asterisk 13.9.1, chan_sip
T46G version 28-81.0.4 and 220.127.116.11.
I register 2 accounts on T46G. I can use account 1 to make call out. If i use account 2 to make call out, the server reply with 403 forbidden. I attached the log information for your reference:
Sending to 10.23.155.34:5060 (no NAT)
Using INVITE request as basis request - email@example.com
Found peer ‘1234’ for ‘7419’ from 10.23.155.34:5060
[Jun 29 13:19:20] WARNING: chan_sip.c:15083 check_auth: username mismatch, have <1234>, digest has <7419>
[Jun 29 13:19:20] NOTICE: chan_sip.c:23612 handle_request_invite: Failed to authenticate device “7419” sip:firstname.lastname@example.org:5060;tag=1458399292
Account 1 is 1234, account 2 is 7419. If i use 7419 to make call out, the server will check the peer information, and use the authentication of 1234 for 7419. Apparently, it auth failed.
Seems that we can change the identify_by option on the server side(PJSIP).
If we use identify_by=username, then we can use 2nd account to make call out.
If we use identify_by=location, then we only can use 1st account to make call out, unless the phone set different port for every single account. On yealink V73, the 1st account us 5060 port, the 2nd account use 5061 account.
To solve the issue, i need to change it on the server sdie (chan_sip), i need your kindly answer my 2 question as below:
- If we change identify_by option to username on chan_sip Asterisk, can we solve this issue?
- How can we change this option on chan_sip asterisk? I think we need to change code to release Asterisk version, right?
- Can you tell me the workload if we need to change Asterisk code? Is it easy?
- If we change the identify_by option by changing asterisk code, will it import other issue to the server?
Thanks in advanced.