<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div style="" class=""><span style="" class="">Hi</span></div><div class="" style="color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span style="" class="">Other side is a Huawei C&C08 Local Exchange.</span></div><div class="" style="color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span style="" class="">I compared Asterisk Trace with C&C08 Trace<br style="" class=""></span></div> <div style="" class=""><br style="" class="">Asterisk side I see ROSE_ETSI_EctInform then ROSE_ETSI_EctLinkIdRequest then Invalid Call State<br style=""
class=""><br style="" class="">At C&C08 I see "OPERATION.........Begin3PTY" and then Invalid Call State<br><br>My Asterisk version !.8.11.0 and Libpri 1.4.12 <br>If I enable 3PTY( 3 party call supplementary service on C&C08) will help?<br><br>Regards<br>babak<br style="" class=""><br style="" class=""><br style="" class=""></div><div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div class="" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div class="" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="" class="" dir="ltr"> <font style="" class="" face="Arial" size="2"> On Monday, June 16, 2014 10:11 PM, Richard Mudgett <rmudgett@digium.com> wrote:<br style="" class=""> </font> </div> <br style="" class=""><br style="" class=""> <div style="" class=""><div
style="" class="" id="yiv7158414472"><div style="" class=""><div style="" class="" dir="ltr"><br style="" class="" clear="none"><div style="" class=""><br style="" class="" clear="none"><br style="" class="" clear="none"><div style="" class="">On Mon, Jun 16, 2014 at 4:05 AM, babak <span style="" class="" dir="ltr"><<a style="" class="" rel="nofollow" shape="rect" ymailto="mailto:bk1379@yahoo.com" target="_blank" href="mailto:bk1379@yahoo.com">bk1379@yahoo.com</a>></span> wrote:<br style="" class="" clear="none">
<blockquote class="" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi<br style="" class="" clear="none">
I have done everything richard told to enable ECT .<br style="" class="" clear="none">
<div style="" class=""><div style="" class="">below is my trace, anyone can help ?<br style="" class="" clear="none">
-- DAHDI/i1/09123278669-4 answered DAHDI/i1/88050048-3<br style="" class="" clear="none">
-- Native bridging DAHDI/i1/88050048-3 and DAHDI/i1/09123278669-4<br style="" class="" clear="none">
PRI Span: 1 Adding facility ie contents to send in FACILITY message:<br style="" class="" clear="none">
PRI Span: 1 ASN.1 dump<br style="" class="" clear="none">
PRI Span: 1 Context Specific/C [1 0x01] <A1> Len:11 <0B><br style="" class="" clear="none">
PRI Span: 1 Integer(2 0x02) <02> Len:1 <01><br style="" class="" clear="none">
PRI Span: 1 <04> - "~"<br style="" class="" clear="none">
PRI Span: 1 OID(6 0x06) <06> Len:6 <06><br style="" class="" clear="none">
PRI Span: 1 <04 00 82 71 01 04> - "~~~q~~"<br style="" class="" clear="none">
PRI Span: 1 ASN.1 end<br style="" class="" clear="none">
PRI Span: 1 INVOKE Component Context Specific/C [1 0x01]<br style="" class="" clear="none">
PRI Span: 1 invokeId Integer(2 0x02) = 4 0x0004<br style="" class="" clear="none">
PRI Span: 1 operationValue OID(6 0x06) = 4.0.369.1.4<br style="" class="" clear="none">
PRI Span: 1 operationValue = ROSE_ETSI_EctLinkIdRequest<br style="" class="" clear="none">
PRI Span: 1<br style="" class="" clear="none">
PRI Span: 1 > DL-DATA request<br style="" class="" clear="none">
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=21<br style="" class="" clear="none">
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 3/0x3) (Sent from originator)<br style="" class="" clear="none">
PRI Span: 1 > Message Type: FACILITY (98)<br style="" class="" clear="none">
PRI Span: 1 TEI=0 Transmitting N(S)=14, window is open V(A)=12 K=7<br style="" class="" clear="none">
PRI Span: 1<br style="" class="" clear="none">
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=21<br style="" class="" clear="none">
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 3/0x3) (Sent from originator)<br style="" class="" clear="none">
PRI Span: 1 > Message Type: FACILITY (98)<br style="" class="" clear="none">
PRI Span: 1 > [1c 0e 91 a1 0b 02 01 04 06 06 04 00 82 71 01 04]<br style="" class="" clear="none">
PRI Span: 1 > Facility (len=16, codeset=0) [ 0x91, 0xA1, 0x0B, 0x02, 0x01, 0x04, 0x06, 0x06, 0x04, 0x00, 0x82, 'q', 0x01, 0x04 ]<br style="" class="" clear="none">
PRI Span: 1<br style="" class="" clear="none">
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=16<br style="" class="" clear="none">
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 3/0x3) (Sent to originator)<br style="" class="" clear="none">
PRI Span: 1 < Message Type: FACILITY (98)<br style="" class="" clear="none">
PRI Span: 1 < [1c 09 91 a3 06 02 01 03 02 01 07]<br style="" class="" clear="none">
PRI Span: 1 < Facility (len=11, codeset=0) [ 0x91, 0xA3, 0x06, 0x02, 0x01, 0x03, 0x02, 0x01, 0x07 ]<br style="" class="" clear="none">
PRI Span: 1 Received message for call 0xa9519f8 on link 0xa83ef9c TEI/SAPI 0/0<br style="" class="" clear="none">
PRI Span: 1 -- Processing IE 28 (cs0, Facility)<br style="" class="" clear="none">
PRI Span: 1 -- Delayed processing IE 28 (cs0, Facility)<br style="" class="" clear="none">
PRI Span: 1 ASN.1 dump<br style="" class="" clear="none">
PRI Span: 1 Context Specific/C [3 0x03] <A3> Len:6 <06><br style="" class="" clear="none">
PRI Span: 1 Integer(2 0x02) <02> Len:1 <01><br style="" class="" clear="none">
PRI Span: 1 <03> - "~"<br style="" class="" clear="none">
PRI Span: 1 Integer(2 0x02) <02> Len:1 <01><br style="" class="" clear="none">
PRI Span: 1 <07> - "~"<br style="" class="" clear="none">
PRI Span: 1 ASN.1 end<br style="" class="" clear="none">
PRI Span: 1 ERROR Component Context Specific/C [3 0x03]<br style="" class="" clear="none">
PRI Span: 1 invokeId Integer(2 0x02) = 3 0x0003<br style="" class="" clear="none">
PRI Span: 1 errorValue Integer(2 0x02) = 7 0x0007<br style="" class="" clear="none">
PRI Span: 1 errorValue = General: Invalid Call State<br style="" class="" clear="none">
PRI Span: 1 ROSE RETURN ERROR:<br style="" class="" clear="none">
PRI Span: 1 INVOKE ID: 3<br style="" class="" clear="none">
PRI Span: 1 ERROR: General: Invalid Call State<br style="" class="" clear="none">
PRI Span: 1<br style="" class="" clear="none">
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=16<br style="" class="" clear="none">
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 3/0x3) (Sent to originator)<br style="" class="" clear="none">
PRI Span: 1 < Message Type: FACILITY (98)<br style="" class="" clear="none">
PRI Span: 1 < [1c 09 91 a3 06 02 01 04 02 01 07]<br style="" class="" clear="none">
PRI Span: 1 < Facility (len=11, codeset=0) [ 0x91, 0xA3, 0x06, 0x02, 0x01, 0x04, 0x02, 0x01, 0x07 ]<br style="" class="" clear="none">
PRI Span: 1 Received message for call 0xa9519f8 on link 0xa83ef9c TEI/SAPI 0/0<br style="" class="" clear="none">
PRI Span: 1 -- Processing IE 28 (cs0, Facility)<br style="" class="" clear="none">
PRI Span: 1 -- Delayed processing IE 28 (cs0, Facility)<br style="" class="" clear="none">
PRI Span: 1 ASN.1 dump<br style="" class="" clear="none">
PRI Span: 1 Context Specific/C [3 0x03] <A3> Len:6 <06><br style="" class="" clear="none">
PRI Span: 1 Integer(2 0x02) <02> Len:1 <01><br style="" class="" clear="none">
PRI Span: 1 <04> - "~"<br style="" class="" clear="none">
PRI Span: 1 Integer(2 0x02) <02> Len:1 <01><br style="" class="" clear="none">
PRI Span: 1 <07> - "~"<br style="" class="" clear="none">
PRI Span: 1 ASN.1 end<br style="" class="" clear="none">
PRI Span: 1 ERROR Component Context Specific/C [3 0x03]<br style="" class="" clear="none">
PRI Span: 1 invokeId Integer(2 0x02) = 4 0x0004<br style="" class="" clear="none">
PRI Span: 1 errorValue Integer(2 0x02) = 7 0x0007<br style="" class="" clear="none">
PRI Span: 1 errorValue = General: Invalid Call State<br style="" class="" clear="none">
PRI Span: 1 ROSE RETURN ERROR:<br style="" class="" clear="none">
PRI Span: 1 INVOKE ID: 4<br style="" class="" clear="none">
PRI Span: 1 ERROR: General: Invalid Call State<br style="" class="" clear="none">
PRI Span: 1<br style="" class="" clear="none">
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=13<br style="" class="" clear="none">
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 4/0x4) (Sent to originator)<br style="" class="" clear="none">
PRI Span: 1 < Message Type: DISCONNECT (69)<br style="" class="" clear="none">
PRI Span: 1 < [08 02 80 90]<br style="" class="" clear="none">
PRI Span: 1 < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: User (0)<br style="" class="" clear="none">
PRI Span: 1 < Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]<br style="" class="" clear="none">
PRI Span: 1 < [1e 02 82 88]<br style="" class="" clear="none">
PRI Span: 1 < Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the local user (2)<br style="" class="" clear="none">
PRI Span: 1 < Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ]<br style="" class="" clear="none">
PRI Span: 1 Received message for call 0xa9760b8 on link 0xa83ef9c TEI/SAPI 0/0<br style="" class="" clear="none">
PRI<br style="" class="" clear="none">
<br style="" class="" clear="none">
Regards<br style="" class="" clear="none">
Maani<br style="" class="" clear="none">
<br style="" class="" clear="none">
</div></div>> This is best asked on the asterisk-users mailing list for the benefit of<br style="" class="" clear="none">
> other people and for list archive searches.<br style="" class="" clear="none">
<br style="" class="" clear="none">
> You haven't mentioned which Asterisk/libpri versions are involved so the<br style="" class="" clear="none">
> functionality may not be available. Only ETSI(EuroISDN) and Q.SIG really<br style="" class="" clear="none">
> support what you are talking about on currently supported Asterisk and libpri<br style="" class="" clear="none">
> versions. Several North American switch types blindly just send a request<br style="" class="" clear="none">
> message to do this but I don't know if it actually works.<br style="" class="" clear="none">
<br style="" class="" clear="none">
> However, there are several reasons why it may not work:<br style="" class="" clear="none">
<br style="" class="" clear="none">
> 1) Asterisk must be configured to do it. The channels in the ISDN span must<br style="" class="" clear="none">
> have transfer=yes, facilityenable=yes, and switchtype=euroisdn or qsig<br style="" class="" clear="none">
> configured in the chan_dahdi.conf file.<br style="" class="" clear="none">
<br style="" class="" clear="none">
> 2) Asterisk must not have any reason to remain in the middle. i.e., The call<br style="" class="" clear="none">
> must be over the same ISDN span with no local channels in the path, no DTMF<br style="" class="" clear="none">
> features enabled on the call (Dial tT type options), and no audio-hooks or<br style="" class="" clear="none">
> frame-hooks attached for things like call recording.<br style="" class="" clear="none">
<br style="" class="" clear="none">
> 3) The peer must be provisioned to allow the feature.<br style="" class="" clear="none">
<br style="" class="" clear="none">
> 4) The peer may not accept the transfer request at the time for other reasons.<br style="" class="" clear="none"></blockquote><div style="" class=""><br style="" class="" clear="none"></div><div style="" class="">Asterisk is attempting to push the tromboned call back to the telco switch.<br style="" class="" clear="none"></div><div style="" class="">However, as shown in the fragment of the call, the peer is rejecting the transfer<br style="" class="" clear="none">
request. Either the peer is not provisioned to allow it or it just does not support<div style="" class="" id="yiv7158414472yqtfd41577"><br style="" class="" clear="none">the functionality.<br style="" class="" clear="none"><br style="" class="" clear="none"></div></div><div style="" class="" id="yiv7158414472yqtfd33078"><div style="" class="">Richard<br style="" class="" clear="none"></div></div></div><div style="" class="" id="yiv7158414472yqtfd13821"><br style="" class="" clear="none"></div></div></div></div></div><br style="" class=""><br style="" class=""></div> </div> </div> </div> </div></body></html>