[asterisk-bugs] [JIRA] (PRI-175) Asterisk Send wrong operation vaule in facility IE for ECT Explicit call transfer

[mehdi Shirazi (JIRA)]

    [ https://issues.asterisk.org/jira/browse/PRI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221191#comment-221191 ] 

mehdi Shirazi commented on PRI-175:
-----------------------------------

while I am waiting for R&D reply I read http://www.itu.int/rec/T-REC-Q.952.7-199706-I
it seems it is explaining ECT implementation in completely different way than ETSI standard.

> Asterisk Send wrong operation vaule in facility IE for ECT Explicit call transfer
> ---------------------------------------------------------------------------------
>
>                 Key: PRI-175
>                 URL: https://issues.asterisk.org/jira/browse/PRI-175
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>         Environment: sip phone -->Asterisk-->EuroISDN-->Local_TDM_Exchange
>            Reporter: mehdi Shirazi
>            Assignee: Richard Mudgett
>         Attachments: analyzer1.png, PABXtrace2.txt, q950.png, sigtrace.txt, T-REC-Q[1].950-200006-I!!PDF-E.pdf
>
>
> sip phone(A) call B  and put call on hold then transfer call to C, A disconnect and B and C connect to each other , Asterisk tries to bypass the call to Local exchange but Local exchange reject by invalid call state.
> first failure report send to Local exchange manufacturer, R&D responed after investigation that PBX(Asterisk)  send wrong operation vaule in facility IE, instead of 06 asterisk send 04, this is operation value for Begin3PTY !.
> I checked with Triton PRI Analyzer , it also shows Asterisk sends 04  according to Q.950 and Q952 06 is for eCTRequest.
> from Asterisk log:
> PRI Span: 1 > [1c 15 91 a1 12 02 01 0b 06 06 04 00 82 71 01 05 30 05 0a 01 01 82 00]
> it seems (...06 06 04...) 04 is wrong and 06 is for eCTRequest and  93 is for ECTLINKIDREQUEST



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