Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-14-2016, 08:57 PM
mamb mamb is offline
Whiz
 
Join Date: Jun 2015
Posts: 26
mamb has 10 reputation points
Default UUI not received from CM for SIP call

Hi,
We are doing a test call/poc to check whether we are able to receive User-to-User (UUI) sent by 3rd party sip dialer and received in TSAPI client application.

setup:
path-1: [sip dialer]-------[Avaya CM-ver-6.0]-------[Avaya CM-ver-5.2]----[Agent VDN]
path-2: [TSAPI client application]-------[AES server]-----[Avaya CM-ver-5.2]

path-1: sip dialer send custom data in SIP header 'User-to-User' & we are able to see in Avaya CM trace (CM MST trace)
But the same is not received in TSAPI Exerciser app & TSAPI client application.

log snippet from MST trace at CM:
==================================
INVITE sip:52347@abc.domain.com:5060;transport=udp SIP/2.0
P-AV-Message-Id: 2_1
Route: <sip:x.x.x.x;transport=tcp;lr;phase=terminating>
Expires: 30
User-to-User: 61626364;encoding=hex

=> all we receive in TSAPI Exerciser is UUI Type: None

we want to receive the UUI data in TSAPI client application but thats not receiving.

In Agent VDN vector step, there is no collect digits & simply route to available agent.
But for testing purpose we havenot logged in any agent for that routing skill.

We made a direct extension call instead of agent vdn and to see UUI is agent phone display, but UUI not displayed.

Is there any configuration missing?
Any step is missing here?
Any configuration to be done in AES?
Please share us on how to troubleshoot & make this work.

Thanks & Regards
Reply With Quote
  #2  
Old 02-04-2016, 11:52 PM
pmulya pmulya is offline
Hot Shot
.
 
Join Date: Oct 2010
Posts: 23
pmulya has 11 reputation points
Default

Hi,

I would suggest you raise case with Avaya CM support teamm for this. The reason being we would have run an ASAI MST on the CM Side to determine whether CM is sending UUI which is received in SIP header over the ASAI messages to AES. AES would be able to provide the UUI to the application over TSAPI only when it has received it from the CM over ASAI.

Hence ASAI MST is important to determine whether CM has sent UUI info over the ASAI.

Thanks,

Prashant
Reply With Quote
  #3  
Old 02-05-2016, 12:08 AM
mamb mamb is offline
Whiz
 
Join Date: Jun 2015
Posts: 26
mamb has 10 reputation points
Default UUI not received from CM for SIP call

Hi Prashant,
Thank you for the reply,

1.The ASAI MST on CM side shows the UUI passed to AES.
2.For tested the same in Avaya SM/CM/AES - all 6.3 environment.
3.In 6.3, TSAPI-client-app recevies UUI data + some additonal special character/unicode characters.
4.The maximul UUI length is 96 bytes;
5.example, uui data converted into hex abc=616263;00C8 - uui shared mode; 03-uui length
SIP dialer sends UUI as 00C803616263
TSAPI excersier=6162634a...
TSAPI application=abcdj
-The expected value should be = abc
6.Any configurations to check in CM or AES side
Thanks
Mahu
Reply With Quote
  #4  
Old 03-16-2016, 02:35 PM
chris180 chris180 is offline
Aspiring Member
 
Join Date: Mar 2016
Posts: 1
chris180 has 10 reputation points
Default RE: UUI not recieved from CM for SIP call

On the agent phone are you checking for uui by using the uui-info button? If so have you changed the COR to allow UUI IE data?

On my system, I could only reliable get UUI info from SM to AES to CTI if in CM I put a collect digit step that used a variable that was set as type "asaiuui", local, and the correct digit length.
Reply With Quote
Reply

Tags
aes, communication manager, user-to-user, uui

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:42 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.