CTI data not passing from SIP to URS

Voice & Telephony
1

Hi , i am having below scenario.

I call into IVR and do a transfer from SIP to Avaya. Agent receiving the call with CTI information
Agent do 1 step transfer to XXXX and call reaches GVP with attach data.
I do transfer from IVR to avaya , the CTI is missing.

When i looked into logs , the attach data is coming in SIP (both the call legs ). CTI data is not coming in URS for second call leg. Any thoughts? Any configuration needed?

2

userdata-map-filter?

3

ISCC?
Correct ISCC method??

Trunk has all correct configuration? ^ (Kubig)

4

Kubig ,

Thanks for responding. In which Configuration? SIP? URS?

Cavagnaro,

ISCC is working and trunk is all having correct configurations

5

Well then post logs, you can’t expect a full answer with just a description

6

Cavagnaro ,

Thanks for your response. In SIP logs you will see all the CTI both the call legs. In URS only it is not coming. If i send the URS , i dont think it wil be useful. Trying to explain logs will be not helpful as this is more a question..

7

Nope, a question is about an specific option.
We have no clue on what your config is, you say it is OK but doesn’t work…so…
With TServer and URS you can see ISCC transactions and objects being called and used.
You expect someone to come up and say “Click button #3” or “change parameter named magic-as-always=on”? Doesn’t work that way…
Logs will reveal where ISCC data (yes, ISCC) is being lost and why

8

Hi ,

Thanks! Please see the below link for logs and let me know

SIP - AttributeConnID 006c029d2d6c9337

https://www.dropbox.com/s/3vhz2sfqptl2psu/logs.zip?dl=0

9

Cavangaro ,

I think in second call leg CTI is not coming.. Is my understandin correct? or if i am missing something let me know

10

Call ends up going to Avaya number 81749901, however I can’t see anything on this DN on Avaya TServer logs. So, is this DN monitored by Genesys? If not, there is no wat ISCC works, Seems a simple transfer call as no ISCC is invoqued for it

11

Thanks for your response , 81749901 is TG - Genesys SIP

12

Say again? Trunk Group? How so?
Doesn’t seem so. Compare first transfer made vs second one to Avaya

13

When the call is released from TServer it goes to GVP (Second Call Leg) , so inorder to route to IVR , we use TG 81749901. When you look after that there will be transfer to 1270001 again..

14

The call (according to the logs) was not routed to the 1270001, but to the 1270002 where the call was just queued. Check your multisite/ISCC configuration to ensure all is configured properly.