Project

General

Profile

Support #4737

How to configure Queries gsup.hlr.123456789.imsi, sip.voice.123.msisdn, smpp.sms.123.msisdn

Added by edgard21031969 26 days ago. Updated 26 days ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
08/31/2020
Due date:
% Done:

0%

Spec Reference:

Description

Hello,

I work on D-GSM to test it with FreeSWITCH, but after configuration, all of my following command give "not-found" answer.

edgard@osmocom-u16-svr:~$ osmo-mslookup-client sip.voice.1001.msisdn
query result last age v4_ip v4_port v6_ip v6_port
sip.voice.1001.msisdn not-found last 0
edgard@osmocom-u16-svr:~$ osmo-mslookup-client gsup.hlr.901700000014701.imsi
query result last age v4_ip v4_port v6_ip v6_port
gsup.hlr.901700000014701.imsi not-found last 0
edgard@osmocom-u16-svr:~$ osmo-mslookup-client gsup.hlr.111111.imsi
query result last age v4_ip v4_port v6_ip v6_port
gsup.hlr.111111.imsi not-found last 0
edgard@osmocom-u16-svr:~$ osmo-mslookup-client gsup.hlr.1001.msisdn sip.voice.10 01.msisdn smpp.sms.1001.msisdn foo.1001.msisdn
query result last age v4_ip v4_port v6_ip v6_port
foo.1001.msisdn not-found last 0
smpp.sms.1001.msisdn not-found last 0
sip.voice.1001.msisdn not-found last 0
gsup.hlr.1001.msisdn not-found last 0
edgard@osmocom-u16-svr:~$ osmo-mslookup-client --csv-headers gsup.hlr.9017000000 14701.imsi
osmo-mslookup-client: unrecognized option '--csv-headers'
Error in command line options. Exiting.
edgard@osmocom-u16-svr:~$ osmo-mslookup-client -f json gsup.hlr.901700000014701. imsi {"query": "gsup.hlr.901700000014701.imsi", "result": "not-found", "last": true, "age": 0}
edgard@osmocom-u16-svr:~$

Did I forget something about queries in my configuration? How can I implemente URL notation, typical mslookup queries look like pleae?
gsup.hlr.123456789.imsi
sip.voice.123.msisdn
smpp.sms.123.msisdn

My osmo-hlr.cfg configuration is:
!
! OsmoHLR example configuration
!
log stderr
logging filter all 1
logging color 1
logging print category 1
logging print category-hex 0
logging print level 1
logging print file basename last
logging print extended-timestamp 1
logging level main notice
logging level db notice
logging level auc notice
logging level ss notice
logging level linp error
!
line vty
bind 127.0.0.1
ctrl
bind 127.0.0.1
hlr
gsup
bind ip 127.0.0.1
bind ip 192.168.43.84
bind ip 0.0.0.0
ipa-name hlr-23
subscriber-create-on-demand 5 cs+ps
subscriber-create-on-demand 5 none
store-imei
mslookup
mdns bind 239.192.23.42 4266
mdns domain-suffix mdns.osmocom.org
mdns bind
server
service sip.voice at 192.168.43.84 5060
service smpp.sms at 192.168.43.84 2775
service gsup.hlr at 192.168.43.84 4222

Thanks to your help

History

#1 Updated by laforge 26 days ago

  • Priority changed from Urgent to Low

What kind of paid support subscription or other entitlement do you think you have to mark your requests as Urgent or High priority?

Also, this is a bug tracker which is used for tracking bugs and feature requests. General usage questions are much better raised at the mailing list. Thanks for your attention.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)