Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-18-2017, 10:43 AM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default Experience Portal Refer Handling with SBC

Hi All,

I'm having an issue to redirect Experience Portal REFER Message from the SBC back to session Manager then to CM.
Actually what is happening now is that:
1- Experience Portal sends REFER Message to Session Manager.
2- Session Manager redirects it to the SBC.
3- SBC takes the REFER message and re-intiate it as RE-INVITE but to the Service Provider not back to the session manager.

I need to know how can I configure the SBC to redirect the REFER message back to the session manager.
Reply With Quote
  #2  
Old 08-21-2017, 07:54 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Genius
 
Join Date: Sep 2010
Location: New York
Posts: 388
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

I had the same problem. I applied an adaptation to the EP SIP entity which prefixed the number with a flag (ex: *9) on ingress (pre-routing). I then defined a new dial pattern for any string beginning with *9 and routed that to CM. On the adaptation applied to CM, strip the *9 on egress.

This will force the Refer message to be routed to CM for processing instead of SM sending it directly to the carrier. I believe SM is using the contents of the Refer-To header to make routing decisions in this scenario.
Reply With Quote
  #3  
Old 08-24-2017, 09:19 AM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default

Quote:
Originally Posted by mlombardi1 View Post
I had the same problem. I applied an adaptation to the EP SIP entity which prefixed the number with a flag (ex: *9) on ingress (pre-routing). I then defined a new dial pattern for any string beginning with *9 and routed that to CM. On the adaptation applied to CM, strip the *9 on egress.

This will force the Refer message to be routed to CM for processing instead of SM sending it directly to the carrier. I believe SM is using the contents of the Refer-To header to make routing decisions in this scenario.
Thanks for the reply. I have applied that but it's still routed to the SP however I have tried the call routing test and it was routed correctly to the CM so it seems that the SM doesn't understand the REFER message. Do you have any suggestion?
Reply With Quote
  #4  
Old 10-02-2017, 09:11 AM
brown834 brown834 is offline
Hot Shot
 
Join Date: Jun 2015
Location: Chesapeake, VA
Posts: 13
brown834 has 10 reputation points
Default

I am not sure if you are still having this issue, but I was able to solve it by setting up a URI Group on the SBC for internal extensions. The URI type is Dial Plan and the URI is XXXX@mycompany.com
Hopefully this helps anyone in the future who has a similar issue.
__________________
Richard C. Browne, Jr.
Telecommunication Engineer
MAP Communications, Inc.
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 06:08 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.