Author Topic: Barge-in Issue  (Read 1847 times)

Offline rht.jedhe

  • Newbie
  • *
  • Posts: 6
  • Karma: 0
Barge-in Issue
« on: October 10, 2013, 01:51:02 AM »
Hi Team,

unfortunately we are facing an strange-issue like unable to barge-in an particular DID (1722236022) number calls but however we able other DID number calls.

for example there are 2 DID numbers using for one of the inboud process which is mentioned below.

one is 1722236022 other one is 61215606.

so here we are unable barge-in any calls for DID number 1722236022  whereas no issue faced when we barge-in to other DID number 61215606 calls.

is there any DID length limitation ? why this particular DID calls unable to barge-in for same environments.

as we are using Genesys 8.1 versions

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Barge-in Issue
« Reply #1 on: October 10, 2013, 02:54:31 AM »
Which component is used to barge, what is setup, how do You barge in, what is call flow, some logs - to get answer it usually makes sense to give more details.

Offline gawix

  • Newbie
  • *
  • Posts: 28
  • Karma: 1
Re: Barge-in Issue
« Reply #2 on: October 28, 2013, 11:11:54 PM »
Maybe your DIDs map to different GVP IVR profiles.  If this is the case, make sure that gvp.service-prerequisite/default-properties-page points to the appropriate defaults-ng.vxml document. Omitting this property can alter barge-in behavior as the original defaults-ng.vxml specify a fetchaudio (which impacts VoiceXML prompt queuing semantic).

Offline genesysbasha

  • Newbie
  • *
  • Posts: 25
  • Karma: 0
Re: Barge-in Issue
« Reply #3 on: October 29, 2013, 02:50:33 PM »
Hi All,

The issue got resolved now. earlier it was not working due to MCU configuration was incorrect.

Thanks