" /> Genesys Mobile Services Callback error - Genesys CTI User Forum

Author Topic: Genesys Mobile Services Callback error  (Read 2808 times)

Offline szs5tim

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Genesys Mobile Services Callback error
« on: October 14, 2017, 09:11:28 PM »
Advertisement
Hi guys,

I am trying to test GMS Callback in a test env and it is not initiating the outbound when I use a customer number starting with + like +49 , but with 0049 it works.
This is the only thing that I can see as relevant in the ORS logs :

22:49:21.580 [T:139857380083456] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='008PS01FGSCTV99B04000VTAES00001C' expression='storeException("Entry1", _event);
App_Last_Error_Event_Name = system.LastErrorEventName;
App_Last_Error_Description = system.LastErrorDescription;' result='' />
22:49:21.580 [T:139857380083456] {ScxmlMetric:3} METRIC <log sid='008PS01FGSCTV99B04000VTAES00001C' expr='ActivityCoreWithParallel.Entry global handler: {
  "data": {
    "description": "Invalid destination specified",
    "error": "invaliddestination",
    "requestid": "b"
  },
  "invokeid": "",
  "name": "error.voice.createcall",
  "sendid": "",
  "type": "platform"
}' label='' level='1' />
22:49:21.580 [T:139857380083456] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='008PS01FGSCTV99B04000VTAES00001C' expression='__Log("ActivityCoreWithParallel.Entry global handler: " + JSON.stringify(_event,null,2));' result='function __Log() {
    [native code]
}' />
22:49:21.580 [T:139857380083456] {ScxmlMetric:3} METRIC <transition sid='008PS01FGSCTV99B04000VTAES00001C' name='Activity.ActivityProcess.CallCustomerFromAgentDN.MakeOutboundCall' event='error.voice.createcall' line='9427' />
22:49:21.580 [T:139857380083456] {ScxmlMetric:3} METRIC <log sid='008PS01FGSCTV99B04000VTAES00001C' expr='error dial attempt: 1/3' label='' level='1' />
22:49:21.580 [T:139857380083456] {ScxmlMetric:3} METRIC <event_queued sid='008PS01FGSCTV99B04000VTAES00001C' name='outbound.schedule' type='internal' />
22:49:21.580 [T:139857380083456] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='008PS01FGSCTV99B04000VTAES00001C' expression='__Log("error dial attempt: " + _data.dialAttempt + "/" + _data._max_dial_attempts);
__Raise("outbound.schedule");
_data.extReportingData['_CB_DIM_FINAL_DIAL_RESULT'] = 'CREATE_CALL_ERROR';' result='CREATE_CALL_ERROR' />
22:49:21.580 [T:139857380083456] {ORSInternal:3} ~OrsEvent[0xafe7ba0]:name=error.voice.createcall
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <event_processed sid='008PS01FGSCTV99B04000VTAES00001C' name='outbound.schedule' disposition='transition selected' duration='0' />
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <transition sid='008PS01FGSCTV99B04000VTAES00001C' name='Activity.ActivityProcess.CallCustomerFromAgentDN.MakeOutboundCall' event='outbound.schedule' line='9437' />
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <log sid='008PS01FGSCTV99B04000VTAES00001C' expr='Setting URS delay until next dial retry attempt' label='' level='1' />
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <event_queued sid='008PS01FGSCTV99B04000VTAES00001C' name='urs.call.routedelay' type='internal' />
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <event_queued sid='008PS01FGSCTV99B04000VTAES00001C' name='method.timer.start._dial_retry_timeout' type='internal' />
22:49:21.581 [T:139857380083456] {ScxmlMetric:3} METRIC <log sid='008PS01FGSCTV99B04000VTAES00001C' expr='Dial retry timer started set to: 300s' label='' level='1' />
22:49:21.581 [T:139857380083456] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='008PS01FGSCTV99B04000VTAES00001C' expression='if (_data.dialAttempt < _data._max_dial_attempts) {
__Log ('Setting URS delay until next dial retry attempt');

var params = {
'duration': _data._dial_retry_timeout
};
__Raise ('urs.call.routedelay', params);

params = {
"name": "_dial_...' result='undefined' />

I get this error.voice.createcall because the number seems to be invalid.
Where is this coming from ?
I use a service configured with agent preview which contacts first the agent and then the agent can initiate the outbound from his DN.

I use SIP Feature Server with a dial plan and I allow basically everything but this request doesn't reach SIP FS at all.I cannot see that in the logs.

Where is this blocked exactly? ???

Thanks!

Offline gen_den

  • Full Member
  • ***
  • Posts: 176
  • Karma: 0
Re: Genesys Mobile Services Callback error
« Reply #1 on: October 16, 2017, 04:27:32 AM »
can you do a manual outbound +49 using your WDE?

Also check this option in  GMS [b]_prefix_dial_out[/b]. but default it is set to either 0 to +

Offline szs5tim

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Genesys Mobile Services Callback error
« Reply #2 on: October 16, 2017, 04:51:32 AM »
[quote author=AK link=topic=10685.msg48509#msg48509 date=1508128052]
can you do a manual outbound +49 using your WDE?

Also check this option in  GMS [b]_prefix_dial_out[/b]. but default it is set to either 0 to +
[/quote]Yes,I can dial out manually from WDE and I am not using any prefix set in GMS.

I also tried using a prefix but then the number is messed up the widget is used because the number is always the prefix+number and then it looks like :  ++49...

Sent from my Galaxy S8 using Tapatalk


Offline gen_den

  • Full Member
  • ***
  • Posts: 176
  • Karma: 0
Re: Genesys Mobile Services Callback error
« Reply #3 on: October 16, 2017, 05:16:05 AM »
what do you see in SIP server logs? Do your SIP server gets the request?

Offline szs5tim

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Genesys Mobile Services Callback error
« Reply #4 on: October 16, 2017, 05:54:20 AM »
[quote author=AK link=topic=10685.msg48513#msg48513 date=1508130965]
what do you see in SIP server logs? Do your SIP server gets the request?
[/quote]I managed to fix this problem.
The ORS gts-core was rejecting the address and then I realized that <createcall> and <consult> elements have a limitation for the "to" attribute by only accepting digits.

So I removed the limit by configuring on the Switch object > Annex tab > gts section the valid-digits and max-digits options.

I used the value : +0123456789

Maybe this will help others if they get into this problem.

Thanks for the support, AK [emoji16]

Sent from my Galaxy S8 using Tapatalk


Offline gen_den

  • Full Member
  • ***
  • Posts: 176
  • Karma: 0
Re: Genesys Mobile Services Callback error
« Reply #5 on: October 16, 2017, 06:12:13 AM »
Great , good to know :)