Realtime PJSIP and multiple AORs

Hi,

I have a following configuration on realtime PJSIP

insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values (101, 'transport-udp', '101', 'testing', 'all', 'yes');
insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values (102, 'transport-udp', '102', 'testing', 'all', 'yes');
insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values (103, 'transport-udp', '103', 'testing', 'all', 'yes');
insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values (104, 'transport-udp', '104', 'testing', 'all', 'yes');
insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values (105, 'transport-udp', '105', 'testing', 'all', 'yes');

insert into ps_endpoints (id, transport, aors, context, allow, direct_media) values ('kamailio', 'transport-udp', '101, 102, 103, 104, 105', 'testing', 'all', 'yes');

When I do pjsip show endpoint kamailio I can see it detects all of the aors

Endpoint:  kamailio                                             Not in use    0 of inf
        Aor:  101                                                1
      Contact:  101/sip:101@xxx:5060             99da980e5a Created       0.000
  Transport:  transport-udp             udp      0      0  0.0.0.0:5060
   Identify:  kamailio/kamailio
        Match: xxx/32

...


 aors                          : 101, 102, 103, 104, 105

But when trying to connect any client but 101 I get an error

AOR '104' not found for endpoint 'kamailio'

When I switch from realtime to standard xxx.conf it works correctly with having multiple aors just comma separated, but in realtime it somehow does not want to work.

Thanks for any help,
– Mateusz

I’d suggest seeing if removing the spaces between the AORs helps… if it does then file an issue[1]. If it doesn’t then also provide the AORs you’ve configured as well and how.

[1] https://issues.asterisk.org/jira

Okay, seems like removing spaces solved the problem. Shame of me I haven’t tried such a simple solution.

Can you file a trivial issue for that? We should be more tolerant.