Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-26-2017, 06:42 AM
bbenwa bbenwa is offline
Member
 
Join Date: Dec 2017
Posts: 3
bbenwa has 10 reputation points
Default Adaption on REFER

I have an application in AEP that transfers back to a VDN through Session Manager. The REFER message has the original caller ID of the caller reaching the application. When the call goes from Session Manager to CM, there seems to be a + added into the FROM and not being removed by the adaption module. Any suggestions to strip this from all fields in SM?
Reply With Quote
  #2  
Old 12-27-2017, 08:41 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 433
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

SM will not manipulate source/origination headers by default. Sounds like there's either an adaptation applied to AEP that is changing the From header on ingress, or an adaptation applied to CM that's changing the From on egress.

Check the adapations applied to these SIP entities and report back. Remember that the + sign counts as a digit in SM and that will affect your min/max values.
Reply With Quote
  #3  
Old 01-11-2018, 06:44 AM
bbenwa bbenwa is offline
Member
 
Join Date: Dec 2017
Posts: 3
bbenwa has 10 reputation points
Default

Quote:
Originally Posted by mlombardi1 View Post
SM will not manipulate source/origination headers by default. Sounds like there's either an adaptation applied to AEP that is changing the From header on ingress, or an adaptation applied to CM that's changing the From on egress.

Check the adapations applied to these SIP entities and report back. Remember that the + sign counts as a digit in SM and that will affect your min/max values.
The adaption has remove for in and outbound calls so this is where it is strange. Nothing is adding, only delete 1 digit if it starts with a 1.

The traceSM logs show the message from the AEP MPP app has TO: "Last, First" <sip:5551234567@domain.com>;tag=1234 but the leg from SM100 to CM has the TO updated to "Last, First" <sip:+5551234567@domain.com>;tag=1234

It has me baffled.
Reply With Quote
Reply

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 12:49 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.