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

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Thu Aug 7 15:00:30 CDT 2014


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

Richard Mudgett commented on PRI-175:
-------------------------------------

I cannot say what is going on with call deflection without seeing traces.  Unfortunately, this is turning into a support request and is not the purpose of the issue tracker.  The issue tracker is for keeping track of bugs in the software which has not been shown here.

You can look at the libpri source to see which supplementary feature specifications that use ASN.1 that are implemented in the rose.c file.

> 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, q952.jpg, 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)



More information about the asterisk-bugs mailing list