GET /api/rest/1.0/routing/state?loginName=oxe7800 HTTP/1.1
Code: Select all
{
"presentationRoutes": [
{
"destinations": [
{
"type": "OFFICE",
"selected": true
},
{
"type": "MOBILE",
"selected": true
}
]
}
],
"forwardRoutes": [
{
"forwardType": "NO_ANSWER",
"destinations": [
{
"type": "VOICEMAIL"
}
]
}
],
"overflowRoutes": [],
"dndState": {
"activate": false
}
}
POST /api/rest/1.0/routing/overflowroute?loginName=oxe7800 HTTP/1.1
Code: Select all
{
"overflowRoutes": [
{
"overflowType": "BUSY",
"destinations": [
{
"type": "NUMBER",
"number": "99980001"
}
]
}
],
"requestId": "PMGR_ecf6d56c-85ae-4c24-8602-112595f78121"
}
Code: Select all
{
"presentationRoutes": [
{
"destinations": [
{
"type": "OFFICE",
"selected": true
},
{
"type": "MOBILE",
"selected": true
}
]
}
],
"forwardRoutes": [
{
"forwardType": "NO_ANSWER",
"destinations": [
{
"type": "VOICEMAIL"
}
]
}
],
"overflowRoutes": [
{
"overflowType": "NO_ANSWER",
"destinations": [
{
"type": "NUMBER",
"number": "99980001"
}
]
}
],
"dndState": {
"activate": false
}
}
I also tried BUSY_NO_ANSWER, same result.. only the NO_ANSWER overflow is set.
It also doesn't matter wheter I remove the NO_ANSWER forward route or not. I believe the fix for showing the proper overflow state doesn't go both ways (you recall that prior to release 29 routing state extraction didn't show the busy overflow route properly), it only shows the config properly but doesn't allow you to set this config properly.