Search results

Jump to: navigation, search

Page title matches

Page text matches

  • ; nodes_sip: json object: node => ip:port of each YateUCN server
    43 KB (5,915 words) - 16:38, 4 September 2017
  • ; nodes_sip: json object: node => ip:port of each openvolte server
    5 KB (778 words) - 17:01, 21 August 2017
  • ...3G) and a Home Subscriber Server (HSS) (4G LTE). The YateHSS/HLR exports a JSON API for integration with any SIM management and CRM systems. It is capable ...r the SS7 configuration interface. For subscriber management you receive a JSON API which you must configure yourself.
    11 KB (1,646 words) - 17:45, 24 February 2017
  • YateHSS/HLR, YateUCN, YateSMSC and YateUSGW all offer a JSON API for configuration. You can use this API to: The JSON API is accessed via the management IP address associated to each server.
    9 KB (1,316 words) - 19:21, 26 July 2018
  • {{DISPLAYTITLE:JSON API for YateHSS/HLR Configuration}}
    13 KB (1,457 words) - 13:21, 26 November 2018
  • YateHSS/HLR provides a JSON API to build your own subscribers management interface/platform. You can al
    44 KB (5,244 words) - 16:13, 5 February 2019
  • ...ith the YateENB (LTE eNodeB module) over S1AP and GTP protocols and uses a JSON API for configuration and management. * [[JSON API for YateUCN Configuration|Configuration and monitoring API]] built in J
    11 KB (1,707 words) - 15:57, 8 October 2019
  • It uses a set/get JSON request to the eNodeB's configuration API from Yate.
    10 KB (1,580 words) - 16:13, 30 August 2018
  • A JSON/HTTP API allows the card reader to be connected to a computer different fro The programmer API inherits the generic [[JSON API]] so it can be installed as a node in [[YateMMI]]. The node name is "si
    7 KB (997 words) - 21:12, 27 February 2018
  • * a JSON API fo subscriber management and configuration 2. [[JSON API]]
    7 KB (1,156 words) - 19:30, 7 February 2017
  • ; The parameter must contain a valid JSON string describing the routing table ; route_table=@${configpath}/node_dra.json
    4 KB (517 words) - 10:53, 14 November 2016
  • == JSON routing table example ==
    17 KB (2,195 words) - 15:44, 21 May 2019
  • ...ith the YateENB (LTE eNodeB module) over S1AP and GTP protocols and uses a JSON API for configuration and management. * [[JSON API]]
    4 KB (565 words) - 15:59, 8 October 2019
  • * [[JSON API for YateDRA Control]] Instructions on how to use the JSON API to retrieve information about node statistics and more.
    999 B (127 words) - 12:04, 10 October 2017
  • YateHSS/HLR exports a JSON API for integration with any SIM management and CRM systems. * [[JSON API]]
    4 KB (480 words) - 09:52, 28 January 2019
  • * [[JSON API]] General information about the JSON API.
    2 KB (231 words) - 12:11, 31 January 2019
  • * [[JSON API]] General information about the JSON API.
    2 KB (225 words) - 10:35, 5 November 2018
  • <!-- * [[JSON API for YateUCN Control]] Instructions on how to use the JSON API to retrieve information about node statistics, data sessions and more.
    833 B (109 words) - 11:38, 31 January 2019
  • * [[JSON API for YateSTP Control]] Instructions on how to use the JSON API to retrieve information about node statistics and more.
    1 KB (193 words) - 16:53, 28 November 2017
  • * [[JSON API]] General information about the JSON API.
    2 KB (274 words) - 13:49, 14 September 2018

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)