Configuration for MM7

March 26, 2020 Contributors

Prior to Momentum version 3.5.6, MM7 domains are configured in the following way:

domain "mm7.example.com" { 
  mm7_xml_schema = "http://www.3gpp.org/ftp/Specs/archive/23_series/ »
    23.140/schema/REL-5-MM7-1-0.xsd" 
  mm7_version = "5.3.0" 
  mm7_mmsc_port = "8080" 
  mm7_http_auth_user = "admin" 
  mm7_http_auth_password = "secret" 
  mm7_mmsc_server = "example.com" 
  mm7_vasid = "test_domain_vas_id" 
  mm7_vaspid = "test_global_vasp_id" 
  mm7_message_class="personal" 
  mm7_delivery_report="true" 
  mm7_inactivity_timer = 300
  generate_bounces = "true" 
}

Note

In Momentum 3.6, domains continue to be configured in the same way as shown in “Configuration prior to 3.5.6”.

As of Momentum version 3.5.6 generic HTTP options replace MM7-specific options. Configure MM7 domains as follows:

domain "mm7.example.com" { 
  http_host = "example.com" 
  http_uri = "/mmssend" 
  mm7_xml_schema = "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ »
    schema/REL-5-MM7-1-0.xsd" 
  mm7_version = "5.3.0" 
  delivery_method = "mm7"
  routes = ( "mm7://example.com/mmssend?port=8080" ) 
  http_basic_auth = "admin:secret" 
  mm7_vasid = "test_domain_vas_id" 
  mm7_vaspid = "test_global_vasp_id" 
  mm7_message_class="personal" 
  mm7_delivery_report="true"
  idle_timeout = 300
  generate_bounces = "true" 
}

The changes are as follows:

  • mm7_mmsc_port and mm7_mmsc_server – These options have been replaced by routes, which specifies the protocol, the server and the port. Note that you must also set the delivery_method to mm7.

  • mm7_http_auth_user and mm7_http_auth_password – These options have been replaced by http_basic_auth.

  • mm7_inactivity_timer – This option has been replaced by idle_timeout.

  • mm7_mmsc_path – This option has been replaced by http_uri.

Additionally, as of version 3.5.6, you must also specify http_host.