-
```
What steps will reproduce the problem?
1. Send through an IPSMGW an SIP/SMS with source address set to alphanumeric
TON, see the attached trace.
2. Boghe client shows the originator address as 37…
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …