similar to: MSNs don't work for me... :(

Displaying 10 results from an estimated 10 matches similar to: "MSNs don't work for me... :("

2004 May 24
1
Chan_capi 0.3.1 , Asterisk , 3 x C4 active ISDN card Segmentation fault
Hi, i use chan_capi 0.3.1 with asterisk (stable branch cvs) and 3 x c4 active ISDN card. From Controller 1 - 7 there are no problems making calls between asterisk and the pstn. But when i make calls from controller 8 - 12 i get on every controller (8 - 12) a segmentation fault in asterisk :( I tried different linux distributions (gentoo 2004.1, redhat 9.0 , suse 9.1) but same error.
2009 Jan 05
1
B410p, Ast1.4, France Télecom Numeris Double T0 problem
Hi. When I call my RNIS numbers (with a mobile phone for example), I can see 2 incoming calls on the IPBX, which should not happend. I'm not sure if it's a problem with the telco France Telecom and their ISDN setup, or if it's a problem with the MISDN driver on the IPBX itself. I'm stuck ... Any advices for troubleshooting that? Someone provide working configuration files
2005 Feb 24
0
Connect to siemens pbx with misdn NT mode
Hi I try to connect my asterisk with a Siemens Hicom pbx. I have a PCI cologne Chip card wich support NT mode. I have compiled mISDN driver, and I use chn_misdn from debian package. The card wotk fine in TE mode but mot in NT mode. for informations : routeur*CLI> misdn show stacks BEGIN STACK_LIST: * Stack Addr: Uid 40200001 Port 1 Type NT Prot. PMP Link DOWN --> bchan: addr 0 channel
2008 Nov 05
0
b410p mIDSN - RNIS signaling problems
Hi. I'm running Asterisk server with 10 sip phones, and 2 grouped T0 lines with 10 DDI numbers. My provider is France Telecom and my setup is : - Debian Lenny - Asterisk 1.4 - Linux kernel 2.6.25.17 - mISDN 1.1.8 driver - Sip phones Thomson ST2030 No problem with the SIP . But when reveiving a call on RNIS line (any of the DDI numbers), the associated SIP phone rings indicating _two_
2003 Oct 20
1
Playing around MSNs
Let's say I have 3 IP phones (A, B, C) and 3 MSNs (1, 2, 3). How can I define that the incoming MSN 1 is redirected to A, 2 to B and 3 to C ? And how can I define that the A phone uses the outgoing MSN 1, etc ? Actually, I'm using the CAPI channel driver, but any help is welcome. Jean-Christophe -------------- next part -------------- An HTML attachment was scrubbed... URL:
2004 May 01
1
Outbound Dialling on ISDN using CAPI - Individual Dial out Plans using msns
Hi All, Could somebody please help me to understand the following: - We have 8 msn's 383590, 383591 etc. What I would like to do is for the person at extension 1 dial out on 383 590, the person at extension 2 dial out on 383 591 etc. I have got myself so confused that I need major help!!! If you could give me a simplistic example, including which files I put the coding in (i.e.
2004 May 04
2
If Then Else Statements - Outbound Dialling on ISDN using CAPI -Individual Dial out Plans using msns
Hi All, Many thanks to Marc who helped me with a previous Capi Dialout plan - however..... What I now would like to be able to do is: - We have 8 msn's 383590, 383591 383592 etc. What I would like to do is set up an If Then Else type statement along the following lines: - If extension 7957 Then Dialout on Capi msn 383590 ElseIf extension 7958 Then Dialout on Capi msn 383591 ElseIf
2004 Dec 02
2
more than 3 msns with chan_capi
I have 10 msns on my isdn bri incoming (AVM Fritz, chan_capi 3.5) When i set in capi.conf [interfaces] msn=1,2,3,4,5,6,7,8,9,10 incomingmsn=* controller=1 softdtmf=1 accountcode= context=tcom-in echocancel=yes devices=2 Only msn 1,2,3 are working. What can i do? Thanks Jens
2005 Aug 02
2
How to let ZAPHFC work with and act on different incoming MSNs?
Hi all, I'm struggling some time now with this problem. Googling and searching on this topic did not deliver the answer yet, so my last hope is this list. Analogue to the things which are possible with modem.conf, where I can configure the MSN's to act on, I would like to have similar functionality. This is the idea: I have 1 ISDN line, it can be reached by 4 different MSN's. I have
2015 Jul 29
2
PJSIP T.38 issues
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your reply Larry. Le 27/07/2015 01:22, Larry Moore a ?crit : > I think the "488 Not acceptable here" is occurring because the channel > connecting through is not T.38 capable, that will be the IAX channel > from iaxmomdem. This is what T38gateway is supposed to do. And I'm very happy to report that after one more