[asterisk-bugs] [JIRA] (SS7-27) [patch] isup timers + q.764 compatibility + new cli commands

Johann Steinwendtner (JIRA) noreply at issues.asterisk.org
Wed Jul 3 10:49:06 CDT 2013


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

Johann Steinwendtner commented on SS7-27:
-----------------------------------------

Yes, this is the fix I have made. But it works in may scenario:
-- Executing [027460122909415 at dial_isdn:26] NoOp("SIP/0537221491-00000001", "Now we really dial") in new stack
-- Executing [027460122909415 at dial_isdn:27] ChanIsAvail("SIP/0537221491-00000001", "DAHDI/g1") in new stack
-- Hungup 'DAHDI/1-1'
-- Executing [027460122909415 at dial_isdn:28] NoOp("SIP/0537221491-00000001", "Status: 0 channel: DAHDI/1-1 cut: DAHDI/1") in new stack
-- Executing [027460122909415 at dial_isdn:29] Dial("SIP/0537221491-00000001", "DAHDI/1/027460122909415,180,") in new stack
I know, it is only a snapshot when the call ist made. I thought it makes the dialplan easier. I will rewrite the dialplan.

I' ve a different issue with colp. the connect number is presented in the way as it is received. (without ss7_apply_plan_to_number)
This is in case ISUP_EVENT_CPG: (event case CPG_EVENT_ALERTING:) and in case ISUP_EVENT_ANM: done on the ast_connected.id.number.str.

Thanks again for your work.
                
> [patch] isup timers + q.764 compatibility + new cli commands
> ------------------------------------------------------------
>
>                 Key: SS7-27
>                 URL: https://issues.asterisk.org/jira/browse/SS7-27
>             Project: LibSS7
>          Issue Type: New Feature
>          Components: NewFeature
>            Reporter: adomjan
>         Attachments: Ast11_v2.diff, btfull-ss7-moreinfo.txt, btfull-ss7.txt, chan_dahdi.c-20080916.patch, chan_dahdi.c-20080918-20081924-1, chan_dahdi.c-20080918.patch, chan_dahdi.c-20080930-full.patch, chan_dahdi.c-20081016-full.patch, chan_dahdi.c-20081024.patch, chan_dahdi.c-20081124.patch, chan_dahdi.c-20081924_1-20081924_2, chan_dahdi.c-20081924_2-20081925_1.patch, chan_dahdi.c-20081924_2-20081926_1.patch, chan_dahdi.c-28-25, chan_dahdi.c-autoacm.patch, chan_dahdi.c_cause_location.diff, chan_dahdi.c-cotfix, chan_dahdi.c-cot_on_previous_cic.patch, chan_dahdi.c-digit_timeout.patch, chan_dahdi.c-echocontrol2-con.patch, chan_dahdi.c-echocontrol.patch, chan_dahdi.c-fixdnid.patch, chan_dahdi.c_forward_indicator.diff, chan_dahdi.c-gra-blocking, chan_dahdi.c-grsfix, chan_dahdi.c-initialhwblo, chan_dahdi.c_itu_switch_doesnt_like_lpa.diff, chan_dahdi.c_little_cot_fix, chan_dahdi.c-mtp3.patch, chan_dahdi.c-no_sus_res-non_isdn_accass.patch, chan_dahdi.c-outofband_busy_congestion, chan_dahdi.c-remove-connected.diff, isup.c-29-21, isup.c-con-patch, isup.c-cot_check_required_into_sam_event.patch, isup.c-cotfix, isup.c-cpgfix, isup.c-fix-cot_in_iam-sam.diff, isup.c-grsfix, isup.c-proper_isup_call_alloc.diff, isup.c-sus_rel, isup.c-varpar2.patch, isup.c-varppar_parser.patch, libss7-20080916.patch, libss7-20080918-20081924-1, libss7-20080918.patch, libss7-20080930-full.patch, libss7-20081016.patch, libss7-20081024.patch, libss7-20081124.patch, libss7-20081924_1-20081924_2, libss7-20081924_2-20081925_1.patch, libss7-20081925_1-20081926_1.patch, libss7_cause_location.diff, libss7-cot_on_previous_cic.patch, libss7_digit_timeout.patch, libss7-echocancelcontrol.patch, libss7-echocontrol2-con.patch, libss7_forward_indicator.diff, libss7-mtp2alarm-cbfix-cleanup.patch, libss7-mtp2-t7.patch, libss7-mtp3.patch, libss7_mtp3_sls_fix.patch, libss7-mtp3_t21.patch, libss7-no_sus_res-non_isdn_accass.patch, libss7-routing-uninhibit-cocb_cleanup.patch, libss7_t8_t27, libss7-tfatfp-1.patch, libss7-tfatfp-2.patch, libss7-tfatfp-3.patch, mtp3.c-fix-netmng-routing, SS7-27_dahdi_27_v1.diff, SS7-27_dahdi_27_v2.diff, SS7-27_dahdi_27_v3.diff, SS7-27_dahdi_27_v4.diff, SS7-27_dahdi_27_v5.diff, SS7-27_dahdi_v10.diff, SS7-27_dahdi_v15.diff, SS7-27_dahdi_v1.diff, SS7-27_dahdi_v2.diff, SS7-27_dahdi_v5.diff, SS7-27_dahdi_v6.diff, SS7-27_dahdi_v6.diff, SS7-27_libss7_1.0_v1.diff, SS7-27_libss7_1.0_v7.diff, SS7-27_libss7_newAPI_v7.diff, SS7-27_libss7_trunk2_v1.diff, SS7-27_libss7_trunk2_v2.diff, SS7-27_libss7_trunk2_v3.diff, SS7-27_libss7_trunk2_v4.diff, SS7-27_libss7_trunk2_v5.diff, SS7-27_libss7_trunk2_v8.diff, SS7-27_libss7_v10.diff, SS7-27_libss7_v12.diff, SS7-27_libss7_v1.diff, SS7-27_libss7_v5.diff, SS7-27_libss7_v6.diff, ss7-bad.txt
>
>
> This path introduce isup timers, + handle the abnormal situation as the q.764 require.
> not complete, isup_gra and the others have to move to call oriantated model.
> enable isup timers, put those lines after the sigchan lines(values just example for testing):
> isup_timer.t1 = 3000
> isup_timer.t5 = 7000
> isup_timer.t7 = 20000
> isup_timer.t12 = 5000 
> isup_timer.t13 = 17000
> isup_timer.t14 = 5000 
> isup_timer.t15 = 17000
> isup_timer.t16 = 5000
> isup_timer.t17 = 17000
> isup_timer.t18 = 5000
> isup_timer.t19 = 17000
> isup_timer.t20 = 5000
> isup_timer.t21 = 17000
> isup_timer.t22 = 5000
> isup_timer.t23 = 17000

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list