Integration in the operator environment

Integration in the operator environment SearchSearch

SMS & MMS Technical Forum » Now.WAP Proxy (Product Support Only) » Integration in the operator environment « Previous || Next »
Author Message
Morezey Dabi
New member
Username: Morezey

Post Number: 4
Registered: 04-2009
Posted on Saturday, April 25, 2009 - 07:48 pm:   

Can some one help me on what is exactly needed to configure the WAP gateway within the operator environment.
I have installed the both NowWAP and NowMMS. My Company wants to integrate both the MMS and WAP gateways after successful tests with the trial version. what do i need to connect the two two the GPRS network, I have sofar managed to have the now mms work over http but have to only work with the registered numbers on the MMSC. Probably a clear diagram will hep with all the interfaces as i have tried configuring using the NowWAP document but I am not successful.
Thanks!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 680
Registered: 08-2008
Posted on Monday, April 27, 2009 - 04:56 pm:   

Hi,

RADIUS is the "missing link".

Your network access servers (GGSN directly, or an existing RADIUS server) need to be configured to forward RADIUS accounting packets to NowWAP.

NowWAP monitors RADIUS activity so that it can match up TCP/IP activity with MSISDN information.

The following document provides the basics:

http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm

Unfortunately, most of the configuration is done on the access server side, so this can vary based upon the equipment that you are using.

It can be difficult to troubleshoot an initial setup of RADIUS because you can't really see it ... so here are a few tips.

1.) When NowWAP receives RADIUS packets, it logs them to separate log files named RADIUS-yyyymmdd.LOG. If you don't see any log files matching this pattern, then this suggests that NowWAP is not seeing any RADIUS requests.

2.) Enabling the WAPDEBUG.LOG can also be helpful for troubleshooting. To enable this log, edit WAPGW.INI, and under the [WAPGW] header, add Debug=Yes. This log will show a hex dump of all received RADIUS packets.

3.) Verify that the NowWAP RADIUS server is listening on the expected port(s).

Stop the NowWAP service. From a command line, run "NETSTAT -a". In the UDP part of the list, you should NOT see "0.0.0.0:1813" listed (this assumes you are using the default RADIUS accounting port of 1813).

Start the NowWAP service and run "NETSTAT -a" again ... you should now see "0.0.0.0:1813" in the UDP ports list. This tells you that NowWAP is actively listening for RADIUS activity on this port.

4.) Disable the Windows firewall to see if this makes a difference.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 5
Registered: 04-2009
Posted on Tuesday, May 05, 2009 - 09:25 am:   

Thanks Des,
I have got two GGSNs one Alcatel and onother from Huawei vendors, the two have the RADIUS component. I can connect directly to them through a router/switch. I however have three more questions?
1. what do i need from the GGSN network? IP adreess?? and what do they require from me? IP, port??
2. From the MSIDN tab on nowWAP how do i specify my now MMSC to forward to? Do i use the hostname or IP adrress? I am using nowmms as the hostname
3.How do i configure nowWAP for wap browsing on a Mobile Phone. what settings/configurations are needed both on the phone and the GGSN?
Thank you for your timely response.
Morezey.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 742
Registered: 08-2008
Posted on Tuesday, May 05, 2009 - 02:29 pm:   

Hi Morezey,

1.) On the GGSN side, you need to define the IP address of NowWAP as a RADIUS accounting server. You might also need to define the RADIUS port number (it may or may not be configurable).

You also need to define a "shared secret" which will be known by GGSN and NowWAP to validate RADIUS packets that are exchanged.

Where it can get more confusing is this...

There are two RADIUS protocols. One is simply known as RADIUS (and is sometimes referred to as RADIUS authentication to differentiate it), and the other is RADIUS accounting.

RADIUS authentication is normally sent over UDP port 1812 (but sometimes is sent over UDP port 1645 because of a typo in the original spec). RADIUS accounting is normally sent over UDP port 1813 (but sometimes is sent over UDP port 1646).

NowWAP is only interested in RADIUS accounting. So if the GGSN has an option to only use a RADIUS accounting server, use that.

If the GGSN does not differentiate, then in NowWAP you should check "Activate Simple Radius Authentication Server". In this case, NowWAP will process both RADIUS protocols.

When RADIUS is activated in NowWAP, whenever NowWAP receives a RADIUS packet, it logs it to a file named RADIUS-yyyymmdd.LOG, so you can check for this file to see if RADIUS packets are being received by NowWAP.

2.) To start with, you can just put a * in this list, which means that NowWAP will include the MSISDN header in all requests that it processes.

If you want to get more specific, put in whatever host name you are using in requests that will be processed by NowWAP (e.g., nowmms if that is the host name).

Note: It's also a good idea to check "Require MSISDN for all gateway connections". When this is set, the gateway will not process any requests unless it has received RADIUS information about the connection.

3.) On the phone, you specify the IP address of NowWAP as the proxy or gateway.

Older phones may not allow a port number to be configured. This indicates that they are using the WSP protocol which is automatically enabled by NowWAP.

For phones that allow a configurable port, you need to define the "HTTP Proxy Port" number to be used on the "HTTP" page of the NowWAP configuration. Then use that same port in the proxy settings on the mobile phone. (8080 is a common port number to be used here.)

Nothing special should be required on the GGSN for this part.


--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 6
Registered: 04-2009
Posted on Thursday, May 07, 2009 - 07:55 am:   

Thanks you Des,
Just a quick question.
How do i connect to a WAP portal e.g wap.google.com?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 750
Registered: 08-2008
Posted on Thursday, May 07, 2009 - 05:24 pm:   

Nothing special required, you generally just request that URL. (Or maybe I am not understanding the question?)
Morezey Dabi
New member
Username: Morezey

Post Number: 7
Registered: 04-2009
Posted on Friday, May 08, 2009 - 01:04 pm:   

You said nothing special should be required on the GGSN for this part. What about the APN. Can I use the same APN used for mms.. or there is a special APN for the WAP Gateways!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 756
Registered: 08-2008
Posted on Friday, May 08, 2009 - 06:10 pm:   

Ah ... now I understand your question a little bit better.

Technically there is no reason that you can't use the same APN for both MMS and WAP traffic.

However, most mobile operators do not.

It becomes more of a billing issue than a technical issue.

In most of the world, the billing model for SMS and MMS is sender pays, and there is no charge for the receiver.

The MMS retrieval process requires that the receiving client make a data connection to an APN to download the message content.

For this reason, a lot of mobile operators create a separate APN for MMS related traffic, and they do not charge for traffic on the MMS APN.

In this scenario, it is important that data traffic on the MMS APN only be able to connect with the MMSC, and not be open for full internet access.

Then you have a separate APN for WAP and internet traffic.

This is what most mobile operators do.

To keep traffic completely separate, you'd typically have a separate WAP gateway for each APN.

However, that's not always practical for smaller/medium size mobile operators. We do have a way that you can have a single WAP gateway that supports both APN ... it is described in the following article:

http://blog.nowsms.com/2008/07/one-wap-gateway-for-both-mms-and.html

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 8
Registered: 04-2009
Posted on Monday, July 20, 2009 - 10:49 am:   

Thank you Des for all the timely responses,
Does the WAP gateway have to be accessible to internet in case it is to be on the same PC with now MMS or not? and if so what ports should be left open in the case the box server is behind a firewall? Just wanted to be sure about this!
Thank you!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1059
Registered: 08-2008
Posted on Tuesday, July 21, 2009 - 05:13 pm:   

Hi Morezey,

It depends on the volume of traffic.

If the WAP gateway is only going to be used for MMS, then in most cases there is no problem installing both NowWAP and NowSMS MMSC on the same PC.

We do, however, recommend that the MMS settings you configure in your mobile phones not use the same IP address for both the WAP Gateway and the MMSC. This gives you flexibility in case at some point in the future you want to make a change and put them on separate PCs.

You can do this easily by using an IP address for the WAP gateway setting, and a host name for the MMSC. (e.g., 1.2.3.4 for the WAP gateway address, and http://mmsc.operator.domain:8080 for the MMSC address) Both can be on the same machine, but it gives you the flexibility to easily separate them if you need to in the future.

It is also possible to bind multiple IP addresses to a single PC, and you can configure both NowWAP and the NowSMS MMSC to only use one of these IP addresses if this is needed for your configuration.

(If you are going to use the WAP gateway only for MMS traffic, we do have a special bundle price offer for NowWAP with the NowSMS MMSC.)

If you are also going to use the WAP gateway for general WAP traffic in addition to MMS traffic, the I would suggest separate PCs.

Regarding firewall questions ...

The WAP gateway needs to have inbound UDP port 9200 and 9201 open to your mobile devices. These ports do not have to be open to the general internet, only to your devices. It also needs to have a configurable inbound TCP port open to your mobile devices for WAP2/HTTP connections. This TCP port number is configurable ... frequently our customers use 8080 as the port number.

RADIUS ports also need to be open, not to general users, but to allow the GGSN or RADIUS server to send RADIUS packets to the WAP gateway.

If the WAP gateway will be serving general browsing traffic, then the WAP gateway needs to be able to make connections out through your firewall to connect to any web services.

If the WAP gateway will only be serving MMS traffic, its firewall should only allow outbound connections to the MMSC.

The MMSC only needs to accept inbound connections on the configured MMSC HTTP port from the WAP gateway.

The only other port that would need to be opened would be if you are using the "Convert to SMS with web link" feature (http://blog.nowsms.com/2008/10/mms-conversion-to-sms-with-web-link.html). In this case, the "Local Server Port" defines a port number that needs to be open for recipients to receive messages. And if you are using this feature, you would normally open this port up to the general internet.


Sorry if that's a little confusing, but hopefully I covered it all.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 9
Registered: 04-2009
Posted on Friday, July 24, 2009 - 07:20 am:   

Thanks you Des, my wap config is working fine! and phones are able to browse, i am also getting the radius feeds very well.
I however need ask something!!
1. What license do you advise for an operation with One million subs on the network and what would be the HardWare requirements..!! Thank you in advance!!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1069
Registered: 08-2008
Posted on Friday, July 24, 2009 - 01:00 pm:   

Hi Morezey,

It depends on how active the users are. In a typical usage scenario, I'd think 1000 concurrent users would be sufficient. You can always watch the usage, and upgrade the license if necessary.

I'd recommend a machine with a quad core processor ... and at this level, I'd recommend running the MMSC and WAP gateway on separate machines.

We're going to be releasing a 64-bit version of NowWAP very soon, and I would recommend using a 64-bit OS and 4GB of memory for NowWAP.

Historically, NowWAP has very little disk space requirement. It only needs disk space for storing log files.

However, this upcoming release offers more reporting options with the log files, and when that's enabled the log file databases are larger. At this size system, you could be looking at about 2GB a day. How much disk space you need depends on how many days you keep the detailed log data for. If you just keep the summary usage reports, they don't take up much space, but you'll probably want to keep 60 to 90 days of detail logs.

For the MMSC, I'd probably start around 3 messages per second. That may be overkill for awhile until usage picks up. If budgeting is tight, I think you could get away with 1mps for quite awhile.

The NowSMS MMSC doesn't use as much memory as NowWAP, so a 32-bit OS is fine. I'd configure 2GB of memory, but NowSMS is only going to use maybe 200MB max ... the rest is good for disk caching.

You might want to talk this over with our sales engineers. Call one of the numbers on the contact form (http://www.nowsms.com/contact.htm), or open up an e-mail dialog with them.

And if you have a preferred hardware vendor, we can look at their current model offerings to help you figure out what would be best.


--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 10
Registered: 04-2009
Posted on Tuesday, August 04, 2009 - 08:06 am:   

Hello Des,
I have installed nowmms on the same server as now wap, i have two NICs and one network interface (10.201.20.40) connects directly to the GGSN and i created a route to the SMSC through the second NIC (10.101.20.109). I am able to send and retrieve MMS using the now mms application on the server. I have configured WAP to send X-MSISDN header to MMSC on 10.101.20.109.
Problem is I cannot send directly from phone to phone. Err "User Not Defined,FAILED"

Below are the configs
==============================================
[MMSC]
MSISDNHeader=X-MSISDN
MSISDNHeaderGateways=10.201.20.*
MSISDNHeaderDefaultCountryCode=256
MSISDNHeaderLocalPrefix=0
MSISDNHeaderAutoProvision=Yes
WebPort=80
SMTPPort=25
RelayHost=
HostName=mms
DomainName=
SMTPRequireAuth=No
EnableDeliveryNotification=Yes
ConvertImages=Yes
ConvertScaleToScreen=Yes
SMSEMail=No
SMSDomainName=
SMSPerEMail=1
NotifyRetryAttempts=2
NotifyRetryDelay=15
IPAddress=10.101.20.109
WAPPushToExternalUsers=Yes
===========================================
[WAPGW]
DefaultHomePage=http://
RestrictByIPAddress=No
HTTPProxyPort=8080
EnableCompression=Yes
WMLCompression=Yes
TunnelNonStandardPorts=Yes
EnableWTCPExtensions=Yes
KeepAliveToClient=300
KeepAliveToServer=90
EnableRadius=Yes
RadiusSecret=orange
IncludeMSISDNForDomain1=*
RadiusAccountingPort=1813
RadiusRequireCLI=No
IncludeMSISDN=Yes
Debug=Yes
IncludeMSISDNForDomain2=10.101.20.109
IncludeMSISDNForDomain3=mms

Kindly advise on what else i have to do! and thank you so much always!!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1119
Registered: 08-2008
Posted on Tuesday, August 04, 2009 - 12:58 pm:   

Hi,

Is it a typo here?

MSISDNHeaderGateways=10.201.20.*

I think you meant:

MSISDNHeaderGateways=10.101.20.*

If that doesn't resolve the problem, then let's look at the debug logs. On the MMSC, enable the MMSCDEBUG.LOG.

On the WAP gateway, edit WAPGW.INI, and under the [WAPGW] header, add Debug=Yes.

Try again, and then post the resulting WAPDEBUG.LOG and MMSCDEBUG.LOG.

Hopefully it's just the typo in the address!

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 11
Registered: 04-2009
Posted on Friday, August 28, 2009 - 12:46 pm:   

It is still not working.. The error i get is that User not defined!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1183
Registered: 08-2008
Posted on Friday, August 28, 2009 - 12:56 pm:   

Enable the WAPDEBUG.LOG by editing WAPGW.INI, and adding Debug=Yes under the [WAPGW] header.

Enable the MMSCDEBUG.LOG by editing WAPGW.INI, and adding Debug=Yes under the [MMSC] header.

Restart the NowSMS MMSC service, and the NowWAP service.

Repeat your attempt.

Post the debug logs in reply here, or e-mail them to nowsms@nowsms.com with "Attention: Des" in the subject line. If you send them via e-mail, post a reply here to tell me to look for the logs.

It sounds like we're not getting the Radius feed in NowWAP ... but the logs will show me exactly what is going on.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 12
Registered: 04-2009
Posted on Tuesday, September 01, 2009 - 09:14 am:   

Hello, I sent you the logs on mail.

Thanks!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1193
Registered: 08-2008
Posted on Tuesday, September 01, 2009 - 12:32 pm:   

Hi Morezy,

Something isn't right.

It seems to be outside of our scope, so let me explain what I see in the hope that you can figure it out.

At 13:02:28:387, we get a notification that xxx790008043 has connected and been assigned IP Address 10.206.14.3.

At 13:04:34:746, we get a notification that this user has disconnected.

At 13:05:04:121, we get a notification that this user has connected again, and has been assigned IP Address 10.206.14.5.

At 13:07:33:652, we are notified that they have disconnected.

At 13:07:51:668, we receive an HTTP POST request (I don't think it's MMS related, it looks like it is for Opera Mini, and the content-type is "application/xml" instead of MMS) from IP address 10.206.14.6. The request is rejected because we don't have any RADIUS information for IP Address 10.206.14.6.

Do you have two access points, and maybe the RADIUS feed is only being received from one of them?

I think NowWAP is working ok, it's just not receiving all of the RADIUS feed.

Hopefully you can figure out the problem by watching the RADIUS-yyyymmdd.LOG and the WAPGW-yyyymmdd.LOG.

The RADIUS-yyyymmdd.LOG will show you the RADIUS accounting information that NowWAP has received. Of particular importance are the "Accounting-Connect" and "Accounting-Disconnect" statements. The "PhoneNumber" and "AssignedIP" parameters tell you what device connected or disconnected.

The WAPGW-yyyymmdd.LOG will report transactions that it received, and what IP address they were received from.

Of particular interest here, you should not be receiving any requests from IP addresses for which an "Accounting-Connect" has not been received.

I hope this helps. I think you've almost got everything configured, but for some reason we are not getting an Accounting-Connect" for your device.

OR ... if your device is the phone number referenced in the log, then maybe the IP address (or port number) of NowWAP is not configured correctly in the phone settings.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 13
Registered: 04-2009
Posted on Wednesday, September 02, 2009 - 08:24 am:   

Thank you Des,
May be to give you some more information!
1.I have defined two APNs, one for browsing traffic and another one for general MMS traffic.
2. I have both applications running on one server windows 2003 OS and i have a 64 bit version of now WAP.
3. I connect directly to the GGSN firewall on IP 10.201.20.1
4. I have implemented Restriction based upon Client IP Addressas below.
A- The server operating system may is configured to be multi-homed on multiple networks (as this is not required, but recommended to allow for possible separation of MMS and browser traffic in the future).
B-. I have two IP addresses configured 10.201.20.4 and 10.201.20.5 with the default gateway 10.201.20.1. On the Now MMS application I specify 10.201.20.5 as the IP address.
C-. From the GGSN it is configured that the MMS-only APN gives out IP addresses on the 10.206.0.0 network and the the other APN, for browser traffic, gives out IP addresses on the 10.205.0.0 network commonly known assigned IP address as observed in the Radius acc. feeds.
D-. On Now WaP applictions config file I added the IncludeMsisdnConnectOnlySourceIP=10.205.*.* to the [WAPGW] section of the WAPGW.INI file, this would tell the WAP gateway that for any requests that come from clients in that IP address range, the gateway should only allow connections to domains/hosts in the "X-MSIDN" list. Connections to the gateway from other client addresses would not be restricted.
5. On the GGSN it,s configured that only MMS APN sends Radius accounting information to the WAP GW and not the browsing APN.
6. On the MMS phone settings I configure the specify 10.201.20.5 as the IP address to use

That all I have..
QNs.
Do I need to have accounting received from browsing APN reason is that we use same APN for both WEB and WAP so when WAP is down we do not need to loose WEB traffic due to radius being down on WAP.

Let me know at this point whether I am missing out something.
Thanks!
Morezey Dabi
New member
Username: Morezey

Post Number: 14
Registered: 04-2009
Posted on Wednesday, September 02, 2009 - 08:37 am:   

application/octet-streamMMSDEBUG.LOG
MMSCDEBUG.LOG (929.8 k)

application/octet-streamWAPDEBUG.LOG
WAPDEBUG.LOG (33.7 k)

application/octet-streamMMS ACCOUNTING
RADIUS-20090902.LOG (6.1 k)


After another attempt today, that is what i got from the MMSDEBUG.LOG after failure to send notification.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1199
Registered: 08-2008
Posted on Friday, September 04, 2009 - 09:13 am:   

Hi Morezy,

It looks like the WAP gateway is not seeing any of the MMS requests. The MMS requests appear to be going directly to the MMSC, without going through the WAP gateway. So I think something is not quite right in the settings on the phone.

I will look for more clues, but so far this is what I see.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 15
Registered: 04-2009
Posted on Monday, September 07, 2009 - 08:47 am:   

Thanks Des,
What settings do advise on the phone? This what the MMSC logs after failing to send.
2009-09-07 12:23:30,MMSIN,10.206.16.22,,,User Not Defined,FAILED
2009-09-07 12:27:41,MMSIN,10.206.16.23,,,User Not Defined,FAILED
2009-09-07 12:28:14,MMSIN,10.206.16.24,,,User Not Defined,FAILED
2009-09-07 12:31:12,MMSIN,10.206.16.25,,,User Not Defined,FAILED
2009-09-07 12:35:17,MMSIN,10.206.16.26,,,User Not Defined,FAILED
2009-09-07 12:36:59,MMSIN,10.206.16.27,,,User Not Defined,FAILED
2009-09-07 12:38:01,MMSIN,10.206.16.28,,,User Not Defined,FAILED,
Thank you!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1204
Registered: 08-2008
Posted on Tuesday, September 08, 2009 - 04:21 pm:   

Hi Morezy,

The names of the settings are a little different on different phones.

Usually, what you will have is an MMS message server URL. In your configuration, you are using http://mms/ (or http://mms) ... this is good.

Then there will be additional connection settings for specifying APN and proxy.

The APN configuration is correct, however after reviewing all of the logs and information above, I think the proxy configuration is a problem.

There is confusion because all applications are currently on the same machine.

I think you have the proxy setting on the phone pointing to port 80. That is the port that the NowSMS MMSC is using, so it sees the request instead of the NowWAP proxy.

The proxy setting on the phone should use port 8080, as that is the port number for which NowWAP is configured.

I think that will resolve the problem. The RADIUS information does seem to be forwarded correctly.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 16
Registered: 04-2009
Posted on Thursday, September 10, 2009 - 05:23 am:   

Hello Des,
I have changed the port to 8080 and points directly to the WAP gateway, Challenge is if i do not supply the home page with the username=password registered in the MMSC it does not work, it only works when the alias is included on the home page. Yet from the logs on the MMSC it is clear that MSISDN header is recieved and interpreted. What should be the exact home page URL in case of automatic provisioning?
Thank you!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1233
Registered: 08-2008
Posted on Thursday, September 10, 2009 - 03:41 pm:   

We're almost there!

There is no need to include anything in the URL.

Post me another MMSCDEBUG.LOG showing a transaction. And also post the current MMSC.INI.

If you're seeing the X-MSISDN header, then we probably just need to tweak the MMSC.INI.

The MMSC.INI that you included earlier should be correct. Specifically these parameters should work based upon what I've seen of your configuration so far.

MSISDNHeader=X-MSISDN
MSISDNHeaderGateways=10.201.20.*
MSISDNHeaderDefaultCountryCode=256
MSISDNHeaderLocalPrefix=0
MSISDNHeaderAutoProvision=Yes

If those are still the parameters you have configured in MMSC.INI, then please post me an MMSCDEBUG.LOG showing another attempt.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 18
Registered: 04-2009
Posted on Monday, September 14, 2009 - 08:26 am:   

Hello Des,
You are totally right, it has now worked out!!

Thank you so much!
application/octet-streamMMSCDEBUG
MMSCDEBUG.LOG (924.1 k)
application/octet-streamMMSC.INI
MMSC.INI (0.5 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1242
Registered: 08-2008
Posted on Monday, September 14, 2009 - 02:35 pm:   

Congratulations!
Morezey Dabi
New member
Username: Morezey

Post Number: 19
Registered: 04-2009
Posted on Wednesday, September 23, 2009 - 06:27 am:   

Hello Des,
I want i need help on implementing MMS charging using accounting call backs, I have read the doc but i need to know the exact parameters to include in the MMSC.INI file.
Thank you very much!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1289
Registered: 08-2008
Posted on Wednesday, September 23, 2009 - 04:31 pm:   

Hi Morezey,

Here's a pretty good write-up on it.

http://blog.nowsms.com/2009/05/mmsc-accounting-callbacks-for-billing.html

Take a look, and then let me know if I can provide any further clarification.

--
Des
NowSMS Support
Morezey Dabi
New member
Username: Morezey

Post Number: 20
Registered: 04-2009
Posted on Friday, September 25, 2009 - 06:09 am:   

Hello Des,
Is there a way of sending XML commands to interact with the billing system?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1302
Registered: 08-2008
Posted on Friday, September 25, 2009 - 07:42 pm:   

No Morezey,

It is only HTTP GET style parameters (URL parameters).

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics