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