[asterisk-bugs] [JIRA] (ASTERISK-29502) res_pjsip_config_wizard: doesn't take into account setting "identify/match"

[Stanislav Abramenkov (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255519#comment-255519 ] 

Stanislav Abramenkov edited comment on ASTERISK-29502 at 7/2/21 5:49 AM:
-------------------------------------------------------------------------

>>>Are you setting "from_user" on the b side to the username to use on a side? That's how matching based on username works.
If I add setting "from_user" on A side(Asterisk 16.19.0), then calls from B side to A side (Asterisk 16.19.0) works fine, but this setting lost callerid. (ext. number)

current setup:
[trunk_name](trunk)
accepts_auth = yes                                      ; Accept incoming authentication from remote hosts. At least inbound_auth/username is required.
accepts_registrations = yes                             ; Accept inbound registration from remote hosts. An AOR with dynamic contacts will be created.
sends_auth = no                                         ; Send outbound authentication to remote hosts. At least outbound_auth/username is required.
sends_registrations = no                                ; Send outbound registrations to remote hosts.
inbound_auth/username = trunk_name
inbound_auth/password = strong_password
endpoint/context = some_context
endpoint/allow = alaw
identify/match = dns_name
endpoint/from_user = trunk_name


>>>Disregarding wizards - why do you have both a registration from b side, and also match based on IP address (therefore you know the IP address making the inbound registration redundant)? Did you do that solve the problem you're now experiencing in the wizard?
Unfortunately, I don't know the IP address, because B side behind DNS. I know only DNS name.

>>>both a registration from b side, and also match based on IP address
Do you mean why not just use IP based trunk without registration ?
If not could you please explain what you mean further?


was (Author: silentindark):
>>>Are you setting "from_user" on the b side to the username to use on a side? That's how matching based on username works.
If I add setting "from_user" on A side(Asterisk 16.19.0), then calls from B side to A side (Asterisk 16.19.0) works fine, but this setting lost callerid. (ext. number)

current setup:
[trunk_name](trunk)
accepts_auth = yes                                      ; Accept incoming authentication from remote hosts. At least inbound_auth/username is required.
accepts_registrations = yes                             ; Accept inbound registration from remote hosts. An AOR with dynamic contacts will be created.
sends_auth = no                                         ; Send outbound authentication to remote hosts. At least outbound_auth/username is required.
sends_registrations = no                                ; Send outbound registrations to remote hosts.
inbound_auth/username = trunk_name
inbound_auth/password = strong_password
endpoint/context = some_context
endpoint/allow = alaw
identify/match = dns_name
endpoint/from_user = trunk_name


>>>Disregarding wizards - why do you have both a registration from b side, and also match based on IP address (therefore you know the IP address making the inbound registration redundant)? Did you do that solve the problem you're now experiencing in the wizard?
Unfortunately, I don't know the IP address, because B side behind DNS. I know only DNS name.

>>>both a registration from b side, and also match based on IP address
Could you please explain to me , what do you mean?

> res_pjsip_config_wizard: doesn't take into account setting "identify/match"
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-29502
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29502
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_config_wizard
>    Affects Versions: 16.19.0
>            Reporter: Stanislav Abramenkov
>            Assignee: Unassigned
>         Attachments: full2.txt, full.txt, pjsip.conf, pjsip_wizard.conf
>
>
> Hello, 
> I have problem with SIP Trunk configuration using PJSIP Wizard.
> It seems that module "res_pjsip_config_wizard.so" doesn't respect (or can't read) setting "identify/match" in Wizard configuration file.
> According to documentation:
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_res_pjsip_config_wizard
> identify/* 	 Variables to be passed directly to the identify.
> Output when I try to configure Trunk using PJSIP Wizard (File pjsip_wizard.conf in attachment)
> CLI> pjsip show endpoint trunk_name
>  Endpoint:  trunk_name                                           Not in use    0 of inf
>      InAuth:  trunk_name-iauth/trunk_name
>         Aor:  trunk_name                                         1
>       Contact:  trunk_name/sip:trunk_name at XXX.XXX.XXX.XXX;tra 7d0851b18e Avail        35.242
> Output when I use PJSIP without Wizard (File pjsip.conf in attachment)
> CLI> pjsip show endpoint trunk_name
>  Endpoint:  trunk_name                                           Not in use    0 of inf
>      InAuth:  trunk_name/trunk_name
>         Aor:  trunk_name                                         1
>       Contact:  trunk_name/sip:trunk_name at XXX.XXX.XXX.XXX;tra 7d0851b18e Avail        35.212
>    Identify:  trunk_name/trunk_name
>         Match: XXX.XXX.XXX.XXX/32



--
This message was sent by Atlassian JIRA
(v6.2#6252)