[asterisk-bugs] [JIRA] (ASTERISK-26333) Problems with Blind Transfer, PJSIP (Aastra 6869i)

[Matthias Binder (JIRA)]

Matthias Binder created ASTERISK-26333:
------------------------------------------

             Summary: Problems with Blind Transfer, PJSIP (Aastra 6869i)
                 Key: ASTERISK-26333
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26333
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: pjproject/pjsip
            Reporter: Matthias Binder


Sangoma told me to open a issue in the asterisk tracker.

We cannot do PJSIP Blind Transfers on the Mitel 6869i Phone.

The Problem is already analysed by Mitel Support and they made a Statement about the problem and showed up a workaround for this problem.

The asterisk pjsip needs to be changed to solve the Problem.

http://community.freepbx.org/t/problems-with-blind-transfer-pjsip-aastra-6869i/34393/20


HI there,

After having a look at the sip traces I have come to the following conclusion:

The Problem:

The channel drivers CHAN_SIP and CHAN_PJSIP seem to implement the REFER method differently.

-- CHAN_SIP responds the REFER with an "202 Accepted" followed by a "200 OK" in NOTIFY sip/frag body as soon as Asterisk knows that the user can be reached.

chan_sip.JPG1361x617 149 KB
-- On the other hand CHAN_PJSIP notifies all the progress details of the C user e.g. Trying, Ringing etc. It sends a "200 OK" ONLY if the called user answers the call.

chan_pjsip1.JPG1419x649 153 KB
chan_pjsip2.JPG1421x667 163 KB
This leads to the stated issue because in case of Blind Transfer, Mitel Phones expect a "200 OK" after REFER has been accepted. Otherwise the line is kept busy. This is by-design with no intension to change it at the moment.




--
This message was sent by Atlassian JIRA
(v6.2#6252)