HTTP enrichment in a private network

HTTP enrichment in a private network SearchSearch
Author Message
FRaveau
New member
Username: Fraveau

Post Number: 13
Registered: 06-2012
Posted on Wednesday, July 25, 2012 - 02:42 pm:   

Hi,

I use Now.WAP to enrich HTTP request to now.SMS. Our handsets and the MMS plateform are in a private network so handset have both private and public addresses.

The radius accounting is received and well anderstood.

The problem is that Now.WAP brings together the MSISDN and private IP (WAPDEBUG.LOG):

Line 348912: (16) - 15:03:43:502 Radius: IP Address 10.6.32.20 = Phone Number 3366422XXXX (3366422XXXX)

But when it request a MMS sending connection, it searches for the MSISDN using the public adress:

Line 1322845: (16) - 15:14:23:727 Radius: IP Address 195.132.255.166 not found

Is there a way to make it search using the private IP?

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4046
Registered: 08-2008
Posted on Wednesday, July 25, 2012 - 03:17 pm:   

Hi,

You need to make sure that there is no network address translation (NAT) between the devices and NowWAP. The devices need to connect to NowWAP using their private IP address.

Currently the request that NowWAP is receiving appears to be coming from a public IP address, such that NowWAP cannot see the private IP address from which the request is originating.

--
Des
NowSMS Support
FRaveau
New member
Username: Fraveau

Post Number: 14
Registered: 06-2012
Posted on Wednesday, July 25, 2012 - 04:08 pm:   

This involves a completly different architecture. There is no workaround?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4047
Registered: 08-2008
Posted on Wednesday, July 25, 2012 - 07:34 pm:   

No, it is necessary that the terminals present their private IP address to the gateway/proxy, in order for the configuration to work.

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: