" /> RequestMuteTransfer - Genesys CTI User Forum

Author Topic: RequestMuteTransfer  (Read 2235 times)

Offline hotsblanc

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
RequestMuteTransfer
« on: April 01, 2010, 06:31:34 PM »
Advertisement
Hello,

I did post same in genesyslabs forums but no luck yet.

I am trying to transfer a call on 2 different CTI stations, one CTI station A and its leg are managed by Genesys, the other one is a SIP inbound call that lands on a different CTI station B.

I am trying to transfer the call on B to CTI station A so that I can then merge legs initially on A and B together on A for audio.

To do this, I currently use RequestMuteTransfer from B to A (A being on hold before transfer). A gets an event ringing which I answer; upon being established I merge the calls.

This is working fine 90% of the time, however from time to time I get the following error after EventPartyChanged ( "Invalid Number/Domain; SIT - Ineffective other"):

[789984] [29 Mar 2010 15:01:27,154] [PublishTask] [INFO ] [Server.TServerLog.13109298 ] - TServer=TServer_Avaya_DEV - tcp://gendev01:3000;Source=com.atx.mctis.server.TServerL istener;TimeInQueue=0;ReadMsg='EventError' (52) attributes: AttributeErrorMessage [str] = "Invalid Number/Domain; SIT - Ineffective other" AttributeReferenceID [int] = 56 AttributeThisDN [str] = "7882" AttributeCustomerID [str] = "Resources" AttributeEventSequenceNumber [long] = 161620 AttributeErrorCode [int] = 600 AttributeTimeinuSecs [long] = 480000 AttributeTimeinSecs [long] = 1269892887;

I am comparing the events flow between a good run and a bad one, and I don't see any difference. I did check the Genesys PBX logs and did not see any extra information about the error.

- Is RequestMuteTransfer a stable feature on Genesys? If not, is there a better alternative? I have tried all others (which are either not supported by PBX or for my use case). A 2 steps transfer with initiate then complete follows the same flow as RequestMuteTransfer (not tried).

- How would I go to solve this problem? This does not seem to be a timing issue and both runs (good and bad) take milliseconds to complete on the correct DNs and conectionIds.

Thank you for any insight, I can post further traces if a bad run if anybody think that could help.

Sebastien.