Difference between revisions of "Charging interfaces of YateSMSC"

From YateBTS
Jump to: navigation, search
(Created page with "== Radius == Radius protocol usage for MO SMS authorization and charging: * YateSMSC sends Access-Request * Request accepted: YateSMSC sends Accounting-Request ** Acct-Status...")
 
(Sample Captures)
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
=== Enable ===
 
=== Enable ===
  
==== Manual ====
+
Edit /etc/yate/smsc/yatesmsc.conf.<br>
Edit /etc/yate/smsc/yatesmsc.conf
+
Add the following:
 
  [general]
 
  [general]
 
  auth_mo_sms_ocs=true
 
  auth_mo_sms_ocs=true
Line 21: Line 21:
 
   
 
   
 
  [radius common]
 
  [radius common]
  ; OCS IP, mandatory
+
  ; IP of Radius server, mandatory
 
  server=1.2.3.4
 
  server=1.2.3.4
 
  ; Password if needed
 
  ; Password if needed
 
  secret=
 
  secret=
 +
 +
=== Sample Captures ===
 +
[[File:radius_mo_sms_auth_ok.txt]]<br>

Latest revision as of 14:04, 31 January 2019

Radius

Radius protocol usage for MO SMS authorization and charging:

  • YateSMSC sends Access-Request
  • Request accepted: YateSMSC sends Accounting-Request
    • Acct-Status-Type: Stop(2)
    • Acct-Input-Packets: 1 (success), 0 if failed to process the SMS

Enable

Edit /etc/yate/smsc/yatesmsc.conf.
Add the following:

[general]
auth_mo_sms_ocs=true

Configuration

Edit /etc/yate/smsc/radius-custom.conf (create the file if missing):

[general]
enable=yes

[radius common]
; IP of Radius server, mandatory
server=1.2.3.4
; Password if needed
secret=

Sample Captures

File:radius mo sms auth ok.txt