Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 07-16-2017, 02:52 PM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default Transfer from Experience Portal to CM Via SIP

Hi All,

I am making a new configuration to switch from H323 to SIP via Session Manager. Till now I can get the call from 3rd Party SBC to Session Manager and from Session Manager to Experience Portal, Where Experience Portal plays an IVR App then it redirects the call to a VDN.

However, in the last step the blind transfer fails from the IVR App on Experience Portal to the VDN.
For Example, the IVR app transferes to VDN 5000 then experience portal translates this to 5000@avaya.com then it is supposed to get back to SM for reidirection to CM but it fails here.
Any one have an idea where the problem could be?
Reply With Quote
  #2  
Old 07-17-2017, 12:47 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 403
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

Is the transfer done via a SIP REFER message? Is there a dial pattern defined in SMGR for 5000 that routes to CM?
Reply With Quote
  #3  
Old 07-17-2017, 01:25 PM
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
Is the transfer done via a SIP REFER message? Is there a dial pattern defined in SMGR for 5000 that routes to CM?
Yes, It's a transfer via SIP REFER message and I have added a dial pattern for 5000 that routes to CM but still fails.
Reply With Quote
  #4  
Old 07-17-2017, 01:28 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 403
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

What is SM doing? Dropping the message and issuing a 4xx error? Check the Refer-To header inside the REFER.
Reply With Quote
  #5  
Old 07-17-2017, 01:50 PM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default

Actually I'm getting 202 Accepted for the REFER Message !
Refer-To Header:
Refer-To: <sip:86663@voice.net;user=phone>
Reply With Quote
  #6  
Old 07-17-2017, 01:54 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 403
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

SM should be passing the REFER to CM who will issue a 202 Accepted response if the extension in the Refer-To header is reachable. Your Refer-To shows EP attempting a transfer to 86663 but you're looking for 5000? Sounds like EP is the issue.
Reply With Quote
  #7  
Old 07-17-2017, 01:56 PM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default

No I was just giving 5000 as an example. The EP application has many VDNs to route to but I have configured 86663 to be routed to the CM, however; I have done a trace on the CM and it's not getting the call at all.

Does Session Manager have to be configured by a differenet way to handle the Refer-To message other than the INVITE?
Reply With Quote
  #8  
Old 07-17-2017, 01:58 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 403
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

It shouldn't. Run traceSM and post the results here. Need to see a ladder diagram of the messages.
Reply With Quote
  #9  
Old 07-17-2017, 02:13 PM
zein1 zein1 is offline
Hot Shot
 
Join Date: May 2013
Posts: 11
zein1 has 10 reputation points
Default

SM-02 VM-MPP5-SV SM100 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------22:00:22.035 |--INVITE-->| | | (108) T:33312736 F:01006622801 U:33312736 P:terminating
22:00:22.036 |<--Trying--| | | (108) 100 Trying
22:00:22.038 |<--Server -| | | (108) 500 Server Link Monitor Status Down
22:00:22.039 |----ACK--->| | | (108) sip:33312736@voice.net:5060
22:00:22.042 |--INVITE-->| | | (108) T:33312736 F:01006622801 U:33312736 P:terminating
22:00:22.079 |<--Trying--| | | (108) 100 Trying
22:00:22.081 | |--INVITE-->| | (108) T:33312736 F:01006622801 U:33312736 P:terminating
22:00:22.091 | |<--Trying--| | (108) 100 Trying
22:00:22.125 | |<--Session-| | (108) 183 Session Progress
22:00:22.127 |<--Session-| | | (108) 183 Session Progress
22:00:22.143 |---PRACK-->| | | (108) sip:33312736@10.38.13.51:5060
22:00:22.144 | |---PRACK-->| | (108) sip:33312736@10.38.13.51:5060
22:00:22.154 | |<--200 OK--| | (108) 200 OK (PRACK)
22:00:22.154 |<--200 OK--| | | (108) 200 OK (PRACK)
22:00:22.568 | |<--200 OK--| | (108) 200 OK (INVITE)
22:00:22.603 |<--200 OK--| | | (108) 200 OK (INVITE)
22:00:22.624 |----ACK--->| | | (108) sip:33312736@10.38.13.51:5060
22:00:22.625 | |----ACK--->| | (108) sip:33312736@10.38.13.51:5060
22:00:50.053 | |<---REFER--| | (108) sip:01006622801@163.121.190.38:5060
22:00:50.054 |<---REFER--| | | (108) sip:01006622801@163.121.190.38:5060
22:00:50.064 |--Accepte->| | | (108) 202 Accepted
22:00:50.065 | |--Accepte->| | (108) 202 Accepted
22:00:50.257 |--NOTIFY-->| | | (108) <sip:33312736@212.103.163.88> Ev:refer
22:00:50.258 | |--NOTIFY-->| | (108) <sip:33312736@212.103.163.88> Ev:refer
22:00:50.269 | |<--200 OK--| | (108) 200 OK (NOTIFY)
22:00:50.270 | |<----BYE---| | (108) sip:01006622801@163.121.190.38:5060
22:00:50.270 |<--200 OK--| | | (108) 200 OK (NOTIFY)
22:00:50.271 |<----BYE---| | | (108) sip:01006622801@163.121.190.38:5060
22:00:50.278 |----BYE--->| | | (108) sip:33312736@10.38.13.51:5060
22:00:50.279 | |----BYE--->| | (108) sip:33312736@10.38.13.51:5060
22:00:50.281 | |<--200 OK--| | (108) 200 OK (BYE)
22:00:50.281 |--200 OK-->| | | (108) 200 OK (BYE)
22:00:50.282 |<--200 OK--| | | (108) 200 OK (BYE)
22:00:50.282 | |--200 OK-->| | (108) 200 OK (BYE)

Last edited by zein1; 07-17-2017 at 02:21 PM.
Reply With Quote
  #10  
Old 02-26-2018, 06:58 AM
jacob207 jacob207 is offline
 
Join Date: Feb 2018
Posts: 1
jacob207 has 10 reputation points
Default

Were you able to resolve this issue? I am having a very similar problem.
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 02:45 PM.

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.