Misleading error message when create profiled subscriber fails: the server is not yet available
Posted: 19 Dec 2018 06:02
My whole license odyssey started with this issue last week (that is now back that the license issue is sorted).
I'm creating UA virtual sets using the profiled subscriber functionality. That used to work until a week ago. Now I'm getting this
Not very helpful I'd dare say. Especially given that other such operations work just fine (e.g. when I create IPTouch devices).
The request being
Turns out (now that I'm looking at it before posting)... Phone_Book_First_Name = null is not something O2G likes. If I put an empty string there, things are back to normal.
I think the behavior should be changed.. this message is highly misleading.
I'm creating UA virtual sets using the profiled subscriber functionality. That used to work until a week ago. Now I'm getting this
Code: Select all
{
"httpStatus": "SERVICE_UNAVAILABLE",
"code": 1000,
"helpMessage": "The server is not yet available. Please retry later if the initialization is not finished.",
"type": "NOT_READY",
"innerMessage": "Connection failed",
"canRetry": true
}The request being
Code: Select all
{
"attributes": [{
"name": "Station_Type",
"value": ["UA_VIRTUAL"]
},
{
"name": "Entity_Number",
"value": ["18"]
},
{
"name": "Directory_Number",
"value": ["1011"]
},
{
"name": "Station_Profil_From",
"value": ["A43010"]
},
{
"name": "Keys_Profil_From",
"value": ["A43010"]
},
{
"name": "Phone_Book_First_Name",
"value": [null]
},
{
"name": "Phone_Book_Name",
"value": ["ssteteam2"]
},
{
"name": "Equipment_Address.Equipment_Address_Rack",
"value": ["255"]
},
{
"name": "Equipment_Address.Equipment_Address_Board",
"value": ["255"]
},
{
"name": "Equipment_Address.Equipment_Address_Terminal",
"value": ["255"]
}]
}I think the behavior should be changed.. this message is highly misleading.