Calling Party Number is NOT displayed at the end of CTI link (CRM), but is displayed on Avaya Phone.

[jhk_7]

Problem persisting only for SIP calls.
When using ISDN signaling, all is good.
There is no problem on CRM side.
What could be a reason ?

 

[jhk_7]

Someone know what s goin on there ?

 

[Wanebo]

Does the CRM system support SIP? Do they state that they interoperate with Avaya? Any DevConnect info on interoperability between it and Avaya? What does the manufacturer say for what header field it reads for the calling party information? You might need to do some sigma or adaptation header manipulation for the CRM to properly pick up the info. Have you done traceSM's to see what is being passed to the CRM?

This could be a lot of things. Start with manufacturer compatibility and work your way up from that.

 

[jhk_7]

I think there cannot be a problem on CRM side, because i've even tested it without CRM, using simple Avaya test tool (AgentView), but during the call, the app is crashing. When we using ISDN with Avaya AgentView, everything is okay. App is working stable and integrating well. This app has the same method of communication with Avaya systems as our CRM, so in my opinion, if the Avaya test tool will not crash (when i will change something to solve the problem), the CRM will also recieve the correct number instead of "unknown

 

[jhk_7]

Hey again !

Can someone halp me and send me full settings of SIP trunk group and signaling group which are you using and they are working well? This info could be helpful.
Thank you in advance!

jhk