[asterisk-bugs] [JIRA] (ASTERISK-28258) DUNDi Does Not Register chan_pjsip Realtime Endpoints On Register

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28258:
------------------------------------------

Note I've applied the patch from for ASTERISK-28238 (https://gerrit.asterisk.org/#/c/asterisk/+/10879/)

I've been unable to duplicate this so far. I've tried it with endpoints, aors, auths, and contacts all configured for realtime, with and without qualifies enabled (e.g. qualify_frequency=30), and tried it with both a udp and tcp endpoint. As well with dynamic and static contacts. Each time the endpoint would appropriately create the extension in the "regcontext".

My contact did show as available though:
{noformat}
*CLI> pjsip show endpoint 103

 Endpoint:  <Endpoint/CID.....................................>  <State.....>  <Channels.>
    I/OAuth:  <AuthId/UserName...........................................................>
        Aor:  <Aor............................................>  <MaxContact>
      Contact:  <Aor/ContactUri..........................> <Hash....> <Status> <RTT(ms)..>
  Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress..................>
   Identify:  <Identify/Endpoint.........................................................>
        Match:  <criteria.........................>
    Channel:  <ChannelId......................................>  <State.....>  <Time.....>
        Exten: <DialedExten...........>  CLCID: <ConnectedLineCID.......>
==========================================================================================

 Endpoint:  103                                                  Not in use    0 of inf
     InAuth:  103/103
        Aor:  103                                               10
      Contact:  103/sip:103 at xx.xx.xx.xx:39638;transport=T df3d566f47 Avail         6.165
  Transport:  transport_tcp             tcp      0      0  0.0.0.0:5060

<snip>

*CLI> pjsip show aor 103

      Aor:  <Aor..............................................>  <MaxContact>
    Contact:  <Aor/ContactUri............................> <Hash....> <Status> <RTT(ms)..>
==========================================================================================

      Aor:  103                                                 10
    Contact:  103/sip:103 at 10.24.19.247:39638;transport=TCP df3d566f47 Avail         6.424


 ParameterName        : ParameterValue
 ==================================================================
 authenticate_qualify : false
 contact              : sip:103 at xx.xx.xx.xx:39638;transport=TCP;ob
 default_expiration   : 3600
 mailboxes            : 
 max_contacts         : 10
 maximum_expiration   : 7200
 minimum_expiration   : 60
 outbound_proxy       : 
 qualify_frequency    : 30
 qualify_timeout      : 3.000000
 remove_existing      : false
 support_path         : false
 voicemail_extension  :

CLI> dialplan show dundi
[ Context 'dundi' created by 'SIP' ]
  '103' =>          1. Noop(103)                                  [SIP]

-= 1 extension (1 priority) in 1 context. =-
{noformat}



> DUNDi Does Not Register chan_pjsip Realtime Endpoints On Register
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-28258
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28258
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_dundi
>    Affects Versions: 13.24.1
>         Environment: CentOS 7.6
>            Reporter: Ross Beer
>            Severity: Minor
>              Labels: pjsip
>
> DUNDi does not register PJSIP endpoints when the configuration is stored in a Realtime database.
> Settings are all stored in the database, including AORs, contacts and endpoints.
> Endpoints show as 'Unavailable' state when registered if qualify is not used, due to a recent change to the qualify process.
> Any endpoints stored in the text config do register with DUNDi and show as available.



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