FollowMe GQL API invalid route

There are two problems with the FollowMe GQL updateFollowMe mutation.

1. If noAnswerDestination is not supplied and no FollowMe exists for the extension then the noAnswerDestination will default to "ext-local,,dest" which is not valid.
2. If noAnswerDestination is set to something like "ext-local,3475,dest" the API returns Invalid Route: ext-local,3912,dest. Full example below.

These two issues combined break the ability to provision a new FollowMe profile.

1. Full Example

1. 1. GQL Mutation

mutation{ updateFollowMe( input:

{ extensionId:"3912" enabled:true strategy: ringallv2prim ringTime:25 followMeList:"3912-700634601" noAnswerDestination: "ext-local,3912,dest" confirmCalls:false ringingMusic:"Ring" initialRingTime:7 enableCalendar:false externalCallerIdMode: default }

) { status message } }

1. 1. Result

Array ( [errors] => Array ( [0] => Array ( [message] => Invalid Route: ext-local,3912,dest [status] => ) ) )