Closed
Bug 948469
Opened 12 years ago
Closed 12 years ago
Direct Billing purchases failure in Hanger
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: karina.filipe, Assigned: payment)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018
Steps to reproduce:
1. Start MarketPlace
2. Search for a paid app
3. Click to purchase
4. Confirm purchase with carrier billing
Region code: Hanger
Device: Unagi
Connection: Wi-Fi
Phone number/MSISDN: +36203751306
Carrier: Telenor
Test App used: PriceTier1
(reproducible in 3G too and all apps available)
Actual results:
The message "Sorry, there was a problem. Please try again later." is displayed and the purchase does not complete.
Expected results:
The purchase should be completed without any issue.
| Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
Bango have investigated and believe this is an operator issue, please investigate
<responseCode>ERROR</responseCode>
<responseMessage>Generic Server Error: Error in Telenor Charged call.Server Error in Request Processing, retry is allowed: Error sending post request to https://api.comoyo.com:4433/partner/payment/v1/acr:c665ab4e29e9fb156f830f9001059e34;ncc=21601;type=Dyna/transactions/amount.Error message: javax.ws.rs.client.ClientException: org.apache.cxf.interceptor.Fault: Could not send Message.
Assignee: nobody → payment
Issue solved for now, problem related to having dynamic IP-addresses on Telenor side and BlueVia not using DNS to resolve changing IPs.
Comment 4•12 years ago
|
||
When you say resolved for now, does this mean it is a temporary fix?
(In reply to payment from comment #3)
> Issue solved for now, problem related to having dynamic IP-addresses on
> Telenor side and BlueVia not using DNS to resolve changing IPs.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
It means that I have not got confirmation that BlueVia have been able to make a permanent fix yet.
Updated•12 years ago
|
Version: 1.4 → 1.5
Updated•12 years ago
|
Flags: affects-hanger+
Updated•12 years ago
|
Priority: -- → P2
Comment 6•12 years ago
|
||
(In reply to payment from comment #5)
> It means that I have not got confirmation that BlueVia have been able to
> make a permanent fix yet.
Can you confirm if this fix is now permanent or whether you are confident enough that the current fix will not break for us to launch?
Updated•12 years ago
|
Flags: needinfo?(payment)
(In reply to Steve Ruston from comment #6)
> (In reply to payment from comment #5)
> > It means that I have not got confirmation that BlueVia have been able to
> > make a permanent fix yet.
>
> Can you confirm if this fix is now permanent or whether you are confident
> enough that the current fix will not break for us to launch?
We are confident that the current fix is working and will not be stopping your launch, it has proved to be working since the fix was implemented mid December
Flags: needinfo?(payment)
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•