|
|
The Parlay X 2.1 interfaces provided by Network Gatekeeper follows the same architecture and structure as the Parlay X 1.0 interfaces. This section provides a description of the Parlay X 2.1 interfaces and how they are supported by Network Gatekeeper.
The Parlay X 2.1 interfaces exposed are compliant with the 3GPP Specification (TS 29.199 2005-12).
In section Parlay X 2.1 interfaces, the endpoints of the web services and which operations supported are stated. For a full description of the interfaces, refer to the specification.
All applications using Parlay X 2.1 must login to WebLogic Network Gatekeeper using the non-Parlay X Access interface in the same manner as applications based on Parlay X 1.0.
This interface returns a login ticket, which must be included in the SOAP header of all subsequent requests. More information on using this interface and on login tickets in general can be found in the section Workflow.
The service endpoint for Access used with Parlay X 2.1 is:http://<IP-address>:<port>/parlayx2/services/Access
To acquire the WSDL file for each service, add ?wsdl to the service endpoint URL. For example:http://<IP-address>:<port>/parlayx2/services/SendSms?wsdl
The notification WSDLs can be found at: http:/<IP-address>:<port>/parlayx2/wsdl/
Where <IP-address> and <port> are the locations at which the Network Gatekeeper is configured to expose the Web Services interfaces.
The WSDL binding style is WS-I basic profile, doc/lit compliant
Network Gatekeeper exposes the following Parlay X 2.1 interfaces:
See the sections below for detailed information about methods and parameters.
The following datatypes an exceptions are supported.
| Note: | In some situations, applications sending SMS or MMS messages need to include charging data as an inline message part. According to specification, this data is to be presented in a ChargingInformation structure |
The Parlay X 2.1 implementation supports this structure, but has a total string length (description + currency + amount + code) limit of 85 characters. If the data length exceeds this limit, a ServiceException, id SVC1005, is thrown.
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/SendSms
Service Endpoint is given by the application
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/ReceiveSms
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/SmsNotificationManager
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/SendMessage
Service Endpoint found at:http:/<IP-address>:<port>/parlayx2/services/ReceiveMessage
Service Endpoint is provided by the application
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/MessageNotificationManager
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/TerminalLocation
Service Endpoint found at:http://<IP-address>:<port>/parlayx2/services/
TerminalLocationNotificationManager
Service Endpoint provided by the application
The Parlay X 1.0 implementation in WebLogic Network Gatekeeper uses a non-standard structure for the senderName parameter in the sendSms, sendSmsLogo and SendSmsRingtone operations of the SendSMS interface and the senderAddress parameter in the sendMessage operation of the SendMessage interface. The format for this string is as follows:
tel:<mailbox ID>\<mailbox password>\tel:<originator address>.
This format continues to be supported for Parlay X 2.1 (It must be used if the application also uses Parlay X 1.0 interfaces.).
The Network Gatekeeper Parlay X 2.1 implementation also supports the specification-defined format for the senderName parameter.
To use this format the mailbox ID and mailbox password must be configured by the operator when the application account is created in the Network Gatekeeper.
|