Re: [Switchfin-devel] Call for help: mISDN problem
Status: Beta
Brought to you by:
dpenev
Menu
▾
▴
Re: [Switchfin-devel] Call for help: mISDN problem
|
From: <swi...@li...> - 2012-04-30 15:27:44
|
Hi Stefan,
Oh, will be able to test in a few days.
Best Regards
Dimitar
----- Original Message -----
From: <swi...@li...>
To: <swi...@li...>
Sent: Monday, April 30, 2012 4:28 PM
Subject: [Switchfin-devel] Call for help: mISDN problem
> Hi guys,
>
> we have used astfin for a long time and now finally try switch to
> switchfin
> as base for our product. While doing this have a problem usind mISDN on
> the
> BRI Appliance. I hope someone of you also had the problem or can give at
> least some hints or tips. We've tested and tried a lot till now but
> running
> out of ideas.
>
> The problem is:
> If there is only one b-channel of an mISDN trunk group in the use you
> cannot
> start an other incomming or outgoing. Even if there are all four BRI ports
> in this trunk group there is only on call possible. If we use four trunk
> groups (one for every BRI interface) we can make one call over every
> interface, but the second one always gets dropped.
>
> Thanks a lot,
> Stefan Leistritz
>
> ======================
> Config and version:
> - build from actual switchfin svn trunk
> - asterisk 1.4.42
> - mISDN: DSS1 Rev. 1.47, ISDN L1 driver version 1.20, ISDN L2 driver
> version
> 1.32
> - misdn-init.conf:
> card = 1,0x4
> te_ptmp = 1,2,3,4
> poll = 64
> dsp_options = 0
> debug = 0
>
> - misdn.conf:
> [general]
> debug = 0
> ntdebugflags = 0
> ntdebugfile = /persistent/var/log/misdn-nt.log
> ;tracefile=/persistent/var/log/asterisk/misdn.log
> ntkeepcalls = no
> bridging = no
> stop_tone_after_first_digit = yes
> append_digits2exten = yes
> dynamic_crypt = no
> crypt_prefix = **
> crypt_keys = test,muh
>
> [default]
> context = misdn
> language = de
> musicclass = default
> senddtmf = yes
> astdtmf = on
> far_alerting = no
> allowed_bearers = all
> nationalprefix = 0
> internationalprefix = 00
> rxgain = 0
> txgain = 0
> te_choose_channel = no
> pmp_l1_check = no
> reject_cause = 16
> need_more_infos = no
> nttimeout = no
> method = standard
> overlapdial = yes
> dialplan = 0
> localdialplan = 0
> cpndialplan = 0
> early_bconnect = yes
> incoming_early_audio = no
> nodialtone = no
> presentation = -1
> screen = -1
> echocancel = 0
> jitterbuffer = 4000
> jitterbuffer_upper_threshold = 0
> hdlc = no
> max_incoming = -1
> max_outgoing = -1
>
> [trunk_m1]
> context = DID_trunk_m1
> ports = 1
> msns = *
> bridging = no
>
>
>
> ======================
> Logs (misdn set debug 5, one BRI in misdn trunk group, one call already
> going on):
>
> Outgoing:
> -- Executing [1-dial@macro-trunkdial-failover-0.3:1]
> Dial("SIP/10-00000001", "mISDN/g:trunk_m1/<number>") in new stack
> P[ 0] --> Group Call group: trunk_m1
> P[ 1] Group [trunk_m1] Port [1]
> P[ 1] portup:1
> P[ 1] channel with stid:10010100 in use!
> P[ 0] channel with stid:0 not in use!
> P[ 0] --> * NEW CHANNEL dad:<number> oad:(null)
> P[ 0] * Queuing chan 0xde4004
> P[ 0] read_config: Getting Config
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> P[ 0] config_jb: Called
> P[ 0] config_jb: Deactivating Jitterbuffer
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:52] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> P[ 0] --> * CallGrp: PickupGrp:
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> P[ 0] --> TON: Unknown
> P[ 0] --> LTON: Unknown
> P[ 0] --> CTON: Unknown
> [Apr 30 13:05:53] WARNING[515]: misdn_config.c:520 misdn_cfg_get: Invalid
> call to misdn_cfg_get! Port number 0 is not valid.
> [Apr 30 13:05:53] NOTICE[515]: chan_misdn.c:4065 add_out_calls: Rejecting
> Outgoing Call on port[0]
> -- Couldn't call g:trunk_m1/<number>
> P[ 0] misdn_release: No Stack found
> == Everyone is busy/congested at this time (0:0/0/0)
>
>
> Incomming:
> P[ 1] handle_frm: frm->addr:42000102 frm->prim:3f082
> P[ 1] channel with stid:10010100 in use!
> P[ 0] channel with stid:0 not in use!
> P[ 1] handle_frm: frm->addr:42000102 frm->prim:30582
> P[ 0] set_channel: bc->channel:0 channel:-1
> P[ 0] NO USERUESRINFO
> P[ 1] lib Got Prim: Addr 42000102 prim 30582 dinfo 20003
> P[ 0] I IND :SETUP oad:<number> dad:4 pid:8 state:none
> P[ 0] --> bc_state:BCHAN_CLEANED
> [Apr 30 13:10:48] WARNING[505]: misdn_config.c:658 misdn_cfg_is_msn_valid:
> Invalid call to misdn_cfg_is_msn_valid! Port number 0 is not valid.
> P[ 0] --> Ignoring Call, its not in our MSN List
> P[ 0] SENDEVENT: no Stack for event:RELEASE_COMPLETE oad:<number> dad:4
> P[ 0] BC_STATE_CHANGE: l3id:20003 from:BCHAN_CLEANED to:BCHAN_CLEANED
> P[ 1] GOT IGNORE SETUP
> P[ 1] Freeing Msg on prim:30582
> P[ 1] Jitterbuffer Underrun. Got 224 of expected 256
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Switchfin-devel mailing list
> Swi...@li...
> https://lists.sourceforge.net/lists/listinfo/switchfin-devel
>
|
