SMS over IMS

[dushy-3474]

Hi @herlesupreeth,

We setup a open5gs and Kamailio without docker. After registering the UEs, Volte calls work fine. But SMS is not working.

We are using Samsung m13 commercial phones, so SMS over IMS support should not be an issue. I have even checked Protocol settings ATTACH REQ IEs, MS network support, There is nothing related to SMS over IMS.

There is on for MT SMS over PS, which is coming as 1 in Attach req logs.

Whenever I send an MO SMS, I can see the following error in the Kamailio cconsole?

resolve.c:1740: str2ipbuf() : invalid name: no conversion to IP address possible

Not sure which IP address and which conf file its talking about.

And also in pcrf.log I can see persiodically the following error can be seen.

CHECK WEBUI : Even the DefaultBearer(QCI:9,ARP:8) cannot support IMS signalling.

But as mentioned above, volte calls are working.

Can you please help here.

Thanks
Dushyanth

[herlesupreeth]

Please attach a wireshark/tcpdump trace when of scenario where you attach both UEs and then send SMS

Also, even if VoLTE call works there is no guarantee that phone prefers to send SMS over IMS. It may prefer to send SMS over circuit switched network. Its completely upto the settings on the phone

[herlesupreeth]

Now
I have added
sip:imsi..@... impu
Implicit set as tel:msisdn

You have to add both tel:msisdn and sip:msisdn@... as implicit set to sip:imsi..@... impu

[dushy-3474]

Hi Supreeth,

After doing the changes suggested above, VoLTE calls stopped working.

As an aside, Would you know what component is responsible for adding "tel:" into the SIP message below (is it scscf, pcscf or icscf, or some block in open5gs/FHoSS)?

#################### START OF MESSAGE #################################
Session Initiation Protocol (MESSAGE)
Request-Line: MESSAGE tel:+7 SIP/2.0
Method: MESSAGE
Request-URI: tel:+7
[Resent Packet: False]
Message Header
[Expert Info (Warning/Undecoded): Trailing stray characters]
[Trailing stray characters]
[Severity level: Warning]
[Group: Undecoded]
Via: SIP/2.0/UDP 10.0.0.172:6102;branch=z9hG4bKaa46.941539fb4f963fd9a7f4f6d089e892fa.0;i=71
Transport: UDP
Sent-by Address: 10.0.0.172
Sent-by port: 6102
Branch: z9hG4bKaa46.941539fb4f963fd9a7f4f6d089e892fa.0
i=71
Via: SIP/2.0/TCP 10.76.0.2:6200;received=10.76.0.2;branch=z9hG4bK-524287-1---352b4570b4f37418;rport=6201;transport=TCP
Transport: TCP
Sent-by Address: 10.76.0.2
Sent-by port: 6200
Received: 10.76.0.2
Branch: z9hG4bK-524287-1---352b4570b4f37418
RPort: 6201
transport=TCP
Max-Forwards: 69
Route: sip:orig@scscf.ims.mnc001.mcc001.3gppnetwork.org:6060;lr
Route URI: sip:orig@scscf.ims.mnc001.mcc001.3gppnetwork.org:6060;lr
Route Userinfo: orig
Route Host Part: scscf.ims.mnc001.mcc001.3gppnetwork.org
Route Host Port: 6060
Route URI parameter: lr
To: tel:+7
SIP to address: tel:+7
From: tel:9000000036;tag=1aaa142b
SIP from address: tel:9000000036
SIP from tag: 1aaa142b
Call-ID: kz2uscNqyEZzMlWyYQWZsA..@10.76.0.2
[Generated Call-ID: kz2uscNqyEZzMlWyYQWZsA..@10.76.0.2]
CSeq: 1 MESSAGE
Sequence Number: 1
Method: MESSAGE
Allow: MESSAGE
Content-Type: application/vnd.3gpp.sms
Supported: path, gruu, sec-agree
User-Agent: Samsung_SM-M136B_VL1_IMS_6.0
Request-Disposition: no-fork
Accept-Contact: *;+g.3gpp.smsip
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=40517200010048000
access-type: 3GPP-E-UTRAN-FDD
utran-cell-id-3gpp: 40517200010048000
Content-Length: 22
P-Charging-Vector: icid-value=4956530A4C0001F24900003200000000; icid-generated-at=10.0.0.172
icid-value: 4956530A4C0001F24900003200000000
icid-generated-at=10.0.0.172
P-Asserted-Identity: tel:9000000036
SIP PAI Address: tel:9000000036
P-Visited-Network-ID: ims.mnc001.mcc001.3gppnetwork.org
Message Body
GSM A-I/F RP - RP-DATA (MS to Network)
Message Type RP-DATA (MS to Network)
RP-Message Reference
RP-Message Reference: 0x10 (16)
RP-Originator Address
Length: 0
RP-Destination Address - (7)
Length: 2
1... .... = Extension: No Extension
.001 .... = Type of number: International Number (0x1)
.... 0001 = Numbering plan identification: ISDN/Telephony Numbering (ITU-T Rec. E.164 / ITU-T Rec. E.163) (0x1)
Called Party BCD Number: 7
RP-User Data
Length: 15
TPDU (not displayed)
GSM SMS TPDU (GSM 03.40) SMS-SUBMIT
0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER
.0.. .... = TP-UDHI: The TP UD field contains only the short message
..0. .... = TP-SRR: A status report is not requested
...0 0... = TP-VPF: TP-VP field not present (0)
.... .0.. = TP-RD: Instruct SC to accept duplicates
.... ..01 = TP-MTI: SMS-SUBMIT (1)
TP-MR: 16
TP-Destination-Address - (9000000032)
Length: 10 address digits
1... .... = Extension: No extension
.000 .... = Type of number: Unknown (0)
.... 0001 = Numbering plan: ISDN/telephone (E.164/E.163) (1)
TP-DA Digits: 9000000032
TP-PID: 0
00.. .... = Defines formatting for subsequent bits: 0x0
..0. .... = Telematic interworking: no telematic interworking, but SME-to-SME protocol
...0 0000 = The SM-AL protocol being used between the SME and the MS: 0
TP-DCS: 0
00.. .... = Coding Group Bits: General Data Coding indication (0)
Special case, GSM 7 bit default alphabet
TP-User-Data-Length: (3) depends on Data-Coding-Scheme
TP-User-Data
SMS text: Ho9

#####################

Regards,
Dushyant

[herlesupreeth]

If you notice in your pcap, that tel is being added by the UE (I think tel:+7 maybe SMSC address programmed in your SIM card). But I noticed that tel:+7 is irrelevant as the SMSC ignores it and only considers the destination address mentioned in SIP body. So I dont think that tel:+7 is the issue.

FHoSS always has been a pain to work with and on top of it even slight misconfiguration will required removing all the subscription details for a SIM and re-provisioning

[dushy-3474]

Hello Supreeth,

Sorry to bug you again. I noticed one thing in the /var/log/syslog
I am attaching the screent shot.
After the i changed the mpath for modules in smsops/examples/kamailio.cfg , Its throwing lot of syntax errors for the uacxxx commands.
Do you have any idea about this?
kamailio.txt

Attaching the kamailio.cfg.

The whole file(kamailio.cfg) is same as in kamailio trunk.
Note: we are starting kamailio with the follwoing.
kamailio -f /usr/local/src/kamailio/src/modules/smsops/examples/kamailio.cfg

Thanks for the help.

[herlesupreeth]

hmm, no idea why its throwing that error. But you can use the cfg file from here - https://github.com/herlesupreeth/docker_open5gs/tree/master/smsc