Alcatel Unleashed

I just set an forward on busy on my set 1033 to 1003, and an associate 7910 (number of my external voicemail).

The OnRoutingStatechanged I receive does not reflect that properly

{
"eventName": "OnRoutingStateChanged",
"loginName": "oxe1033",
"routingState": {
"activableProfiles": [],
"presentationRoutes": [{
"destinations": [{
"type": "OFFICE",
"selected": true
}]
}],
"forwardRoutes": [],
"overflowRoutes": [{
"overflowType": "NO_ANSWER",
"destinations": [{
"type": "VOICEMAIL"
}]
}]
}
}

We can see the voicemail as associate, but that's not correct.. the immediate forward was set to 1003.

I also have an OTMS.. the same event looks as follows

{
"eventName": "OnRoutingStateChanged",
"loginName": "alcateltest5",
"routingState": {
"appliedProfile": {
"id": "1",
"name": "BUSINESS_ONLY",
"defaultProfile": true
},
"activableProfiles": [{
"id": "1",
"name": "BUSINESS_ONLY",
"defaultProfile": true
}],
"presentationRoutes": [{
"destinations": [{
"type": "OFFICE",
"deviceId": "1033",
"number": "1033",
"acceptable": true,
"selected": true
},
{
"type": "PC",
"deviceId": "99921033",
"number": "99921033",
"acceptable": true,
"selected": false
},
{
"type": "MOBILE",
"acceptable": false,
"selected": false
},
{
"type": "HOME",
"acceptable": false,
"selected": false
},
{
"type": "OTHER",
"acceptable": false,
"selected": false
}]
}],
"forwardRoutes": [{
"forwardType": "BUSY",
"destinations": [{
"type": "VOICEMAIL",
"acceptable": false,
"selected": false
},
{
"type": "USER",
"acceptable": true,
"selected": false
},
{
"type": "NUMBER",
"number": "1003",
"acceptable": true,
"selected": true
}]
}],
"overflowRoutes": [{
"overflowType": "NO_ANSWER",
"destinations": [{
"type": "ASSOCIATE",
"number": "7910",
"acceptable": true,
"selected": true
}]
}],
"currentDeviceId": "1033"
}
}

As you can see, the associate has been set, and it is of type NO_Answer (makes sense, associate is always no answer), and we have the forward to 1003 of type busy.

So, all correct on OTMS, but wrong on O2G.

Here a possible answer:

The device is oxe70120 with a other subscriber number as associate
==============================================================
1)
POST http://172.25.152.156/api/rest/1.0/routing/forwardroute
{ "forwardRoute":
{ "forwardType": "BUSY",
"destinations": [
{ "type": "VOICEMAIL" }
]}}
===> Notification
{"eventName":"OnRoutingStateChanged","loginName":"oxe70120","routingState":{"activableProfiles":[],"presentationRoutes":[{"destinations":[{"type":"OFFICE","selected":true}]}],
"forwardRoutes":[{"forwardType":"BUSY","destinations":[{"type":"VOICEMAIL"}]}],"overflowRoutes":[]}}

2)
Forward disable
===> Notification
{"eventName":"OnRoutingStateChanged","loginName":"oxe70120","routingState":{"activableProfiles":[],"presentationRoutes":[{"destinations":[{"type":"OFFICE","selected":true}]}],
"forwardRoutes":[],"overflowRoutes":[]}}

The device is oxe70120 with a voicemail number as associate
==============================================================
3)
POST http://172.25.152.156/api/rest/1.0/routing/forwardroute
{ "forwardRoute":
{ "forwardType": "BUSY",
"destinations": [
{ "type": "VOICEMAIL" }
]}}
===> Notification
{"eventName":"OnRoutingStateChanged","loginName":"oxe70120","routingState":{"activableProfiles":[],"presentationRoutes":[{"destinations":[{"type":"OFFICE","selected":true}]}],
"forwardRoutes":[{"forwardType":"BUSY","destinations":[{"type":"VOICEMAIL"}]}],"overflowRoutes":[]}}

4)
Forward disable
===> Notification
{"eventName":"OnRoutingStateChanged","loginName":"oxe70120","routingState":{"activableProfiles":[],"presentationRoutes":[{"destinations":[{"type":"OFFICE","selected":true}]}],
"forwardRoutes":[],"overflowRoutes":[{"overflowType":"NO_ANSWER","destinations":[{"type":"VOICEMAIL"}]}]}}

Yes: it is a bug: the notification OnRoutingStateChanged must reflect the whole routing state of the user, like the GET /routing/state response does, and not only the last operation result.
In your case, the forward should also appear too.

==> TO BE FIXED