Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Avaya Aura & Unified Communications (http://support.avaya.com/forums/forumdisplay.php?f=2)
-   -   Transfer from Experience Portal to CM Via SIP (http://support.avaya.com/forums/showthread.php?t=12888)

zein1 07-16-2017 01:52 PM

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?

mlombardi1 07-17-2017 11:47 AM

Is the transfer done via a SIP REFER message? Is there a dial pattern defined in SMGR for 5000 that routes to CM?

zein1 07-17-2017 12:25 PM

Quote:

Originally Posted by mlombardi1 (Post 31568)
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.

mlombardi1 07-17-2017 12:28 PM

What is SM doing? Dropping the message and issuing a 4xx error? Check the Refer-To header inside the REFER.

zein1 07-17-2017 12:50 PM

Actually I'm getting 202 Accepted for the REFER Message !
Refer-To Header:
Refer-To: <sip:86663@voice.net;user=phone>

mlombardi1 07-17-2017 12:54 PM

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.

zein1 07-17-2017 12:56 PM

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?

mlombardi1 07-17-2017 12:58 PM

It shouldn't. Run traceSM and post the results here. Need to see a ladder diagram of the messages.

zein1 07-17-2017 01:13 PM

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)

jacob207 02-26-2018 05:58 AM

Were you able to resolve this issue? I am having a very similar problem.


All times are GMT -7. The time now is 09:47 PM.