UnwiredtecDocumentation : EnterflexMessagingMQubeVerizon

This provider is added for internal needs of MM

Verizon do not support wap pushes. It provides MMS API instead. But you have to specify &transfer=wap when you access Enterflex anyway. And this is the only transfer supported by Enterflex for this carrier.

List of properties to be specified for the carrier (in enterflex.properties):

delivery.mqube.mqubeUrl – url of MQube gateway to connect to
delivery.mqube.password – password to be used for MQube gateway authentificatation
delivery.mqube.user-name – username to be used for MQube gateway authentificatation

Additional request parameter should be added:

user-agent – MQube handset id is passed here. See MQube documentation for more details. There are two ways to obtain the handset id. It can be stored for each phone on your side and passed each time or it can be obtained using specific discovery request, which is described later on this page.

Simulation of Content download confirmation callbacks

In order to simulate functionality equal to Content download confirmation callbacks, that is described here, callbacks are sent to the Content download confirmation callbacks url each time delivery notification comes from Verizon. So when Verizon confirms that mms message was successfully delivered to the device, you are able to get notification about it and make required operations (bill message, ...).

Please note that standard delivery notification is also launched so if you have both callback urls specified in enterflex.properties, you will get callbacks to each of them for delivery notification messages (and not for send notification messages – send notification messages will be sent only to delivery notification url). See more about send notification and delivery notification here.

Discovery request

If you do not know the verizon handset id when sending message, you can use additional functionality, provided by Verizon: “Discovery Message”. You send any simple content (image) to the verizon and mark it as a free “discovery” message. Message is delivered to subscriber. When user downloads it, Content download confirmation callback is sent by Enterflex to your url with one additional parameter &discovery=true.

You extract user-agent from the Content download confirmation callback and send next request to Enterflex with the user-agent provided.

Example:

First request is sent using utilityname send, which sends specified content without any adaptation.

http://yoursite.com/gateway/?utilityname=send&content-url=http://site2.unwiredtec.com/samples/images/tul.jpg&browser-access-disabled=false&discovery=true&from=39999&to=6503933591&routings-list-task=mqube-verizon-routings-list&content-type=image/jpeg&text=discovery%20request

callback that you will get to your Content download confirmation url:

http://yourcallbacksite?to=6503933591&discovery=true&user-agent=audio8900&details=Retrieved&callback-date=11%20Feb%202008%2012:21:11%20GMT&from=39999&status=SUCCESS&ip=64.14.95.24&id=NPPPXSOVISJ9FV8VFBEV

So you can extract user-agent=audio8900 field and specify it in your content upload request.

For example here we are sending image to the phone:

http://yoursite.com/gateway/?utilityname=send-adapted&content=040&domain=image&routings-list-task=mqube-verizon-routings-list&to=16503933591&from=39999&storage=efl_sherri&user-agent=audio8900

MQube Verizon Forward Lock

When you specify parameter &drm=FL or &drm=CD or &drm=SD or &drm=auto special MQube Verizon flow is launched instead of standart drm functionality. Adapted content is not packed with DRM, but additional mqube parameter is passed when sending mms message through mqube gateway, that tells mqube to provide forward lock.