Hi All,
I have a situation where a device has successfully registered and its location saved/stored in memory.
I can see all the stored information when I issue a "kamctl ul show"
However, if I perform a kamctl ul show subscriber@domain, where the 'subscriber@domain' is copied/pasted from the output of the "kamctl ul show" command, it results in an AOR not found error. However, with other AOR's on the same registrar, the "kamctl ul show subscriber@domain" works.
I checked the usernames for the failed commands, and I dont see anything obvious, they are a combination of lower/upper-case leters and digits. String length is around 24 characters for the username (the username table for the subscriber is 64 characters). I'm not sure what elese to check to see why the AOR lookup for these particular clients are failing when they are indeed registered. All other functions around the lookup seem to work, for example, a location lookup for these AOR's are working.
I wonder if I have come accross an issue with the kamctl function and/or the equivilient xmlrpc ul.lookup method.
Any thoughts on this would be greatly appreciated.
Thanks
sorry, I forgot to mention, I am using kamailio v4.3.1:
# kamailio -V version: kamailio 4.3.1 (x86_64/linux) f38e67 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: f38e67 compiled on 18:15:23 Jul 20 2015 with gcc 4.4.7
On 21/07/2015 15:11, Asgaroth wrote:
Hi All,
I have a situation where a device has successfully registered and its location saved/stored in memory.
I can see all the stored information when I issue a "kamctl ul show"
However, if I perform a kamctl ul show subscriber@domain, where the 'subscriber@domain' is copied/pasted from the output of the "kamctl ul show" command, it results in an AOR not found error. However, with other AOR's on the same registrar, the "kamctl ul show subscriber@domain" works.
I checked the usernames for the failed commands, and I dont see anything obvious, they are a combination of lower/upper-case leters and digits. String length is around 24 characters for the username (the username table for the subscriber is 64 characters). I'm not sure what elese to check to see why the AOR lookup for these particular clients are failing when they are indeed registered. All other functions around the lookup seem to work, for example, a location lookup for these AOR's are working.
I wonder if I have come accross an issue with the kamctl function and/or the equivilient xmlrpc ul.lookup method.
Any thoughts on this would be greatly appreciated.
Thanks
Hi,
Any thoughts on this, I can provide actual examples for this, however, I would rather not send valid subsciber info directly to the list.
If anyone is available for looking into it I can send the relevent information/examples directly to them.
Thanks
On 21/07/2015 15:11, Asgaroth wrote:
Hi All,
I have a situation where a device has successfully registered and its location saved/stored in memory.
I can see all the stored information when I issue a "kamctl ul show"
However, if I perform a kamctl ul show subscriber@domain, where the 'subscriber@domain' is copied/pasted from the output of the "kamctl ul show" command, it results in an AOR not found error. However, with other AOR's on the same registrar, the "kamctl ul show subscriber@domain" works.
I checked the usernames for the failed commands, and I dont see anything obvious, they are a combination of lower/upper-case leters and digits. String length is around 24 characters for the username (the username table for the subscriber is 64 characters). I'm not sure what elese to check to see why the AOR lookup for these particular clients are failing when they are indeed registered. All other functions around the lookup seem to work, for example, a location lookup for these AOR's are working.
I wonder if I have come accross an issue with the kamctl function and/or the equivilient xmlrpc ul.lookup method.
Any thoughts on this would be greatly appreciated.
Thanks
FYI
I open issue #264 on github for this oddity I'm experiencing.
On 22/07/2015 11:41, Asgaroth wrote:
Hi,
Any thoughts on this, I can provide actual examples for this, however, I would rather not send valid subsciber info directly to the list.
If anyone is available for looking into it I can send the relevent information/examples directly to them.
Thanks
On 21/07/2015 15:11, Asgaroth wrote:
Hi All,
I have a situation where a device has successfully registered and its location saved/stored in memory.
I can see all the stored information when I issue a "kamctl ul show"
However, if I perform a kamctl ul show subscriber@domain, where the 'subscriber@domain' is copied/pasted from the output of the "kamctl ul show" command, it results in an AOR not found error. However, with other AOR's on the same registrar, the "kamctl ul show subscriber@domain" works.
I checked the usernames for the failed commands, and I dont see anything obvious, they are a combination of lower/upper-case leters and digits. String length is around 24 characters for the username (the username table for the subscriber is 64 characters). I'm not sure what elese to check to see why the AOR lookup for these particular clients are failing when they are indeed registered. All other functions around the lookup seem to work, for example, a location lookup for these AOR's are working.
I wonder if I have come accross an issue with the kamctl function and/or the equivilient xmlrpc ul.lookup method.
Any thoughts on this would be greatly appreciated.
Thanks
-
Asgaroth