search for: incomingmsn

...cemail msn of that users telephone. The Problem is: The PBX supports a too small number of msns, so I can't give every user a voicemailbox. Mailboxes are assigned after different contexts (in capi.conf the "msn" option). It would be extremely cool, to create new contexts after "incomingmsn", I would only use up 1 msn for all voicemailboxes, and call the context according to the telephone of the user, that was called in his/her absence. Now, that does not work though. The incomingmsn apparently doesn't create a new context. Or does it? Is there a way to do that? Here a dia...

...umbers) X (99 Indial extensions) eg: BAAAAAA00 BAAAAAA20 etc Requirement: - To be able send Indial numbers as Caller ID when dialing out. Configration: capi.conf --------- [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 [interfaces] mode=immediate isdnmode=ptp msn=BAAAAAA incomingmsn=* controller=1 softdtmf=1 accountcode= context=main-menu usecallerid=yes callerid=asreceived ;echosquelch=1 ;echocancel=yes ;echotail=64 callgroup=1 pickupgroup=1 devices=2 mode=immediate isdnmode=ptp msn=BAAAAAA incomingmsn=* controller=2 softdtmf=1 accountcode= context=main-menu usecallerid=yes...

...use mISDN with capi, so capi.conf is edited. I have tested both separate and cards are working well. But they are not working together. It seems that when i set up settings for the other card: ;capi.conf: [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 [interfaces] msn=50 incomingmsn=* controller=1 softdtmf=0 context=demo devices=2 msn=50 incomingmsn=* controller=2 softdtmf=0 context=demo devices=2 only controller 1 is working. capiinfo shows me both cards properly. when i tried this capi.conf configuration: [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain...

...lprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 ;ulaw=yes ;set this, if you live in u-law world instead of a-law [123456] ; Master number for line - i.e. number for line before MSNs were allocated ; and which still works and still accepts incoming calls. isdnmode=msn msn=01234123456 ;incomingmsn=* incomingmsn=123456 controller=1 softdtmf=1 accountcode= context=isdn-in echosquelch=1 echocancel=yes ;echotail=64 ;callgroup=1 ;deflect=12345678 devices=2 [123457] ;first MSN msn=01234123457 ;incomingmsn=* incomingmsn=123457 isdnmode=msn controller=1 softdtmf=1 accountcode= context=isdn-in echos...

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

...VM 4 with 3 BRI lines and 1 ISDN-phone (Extens: 251). At the moment only the 3 BRI lines were connected. Do you know how to do that? Maybe like this: /etc/asterisk/capi.conf ; ; CAPI config ; ; [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 [ISDN2] isdnmode=ptp msn=51 incomingmsn=251 controller=4 softdtmf=1 accountcode= context=Amt callgroup=2 devices=2 [ISDN1] isdnmode=ptp msn=3899231 incomingmsn=* controller=1,2,3 softdtmf=1 accountcode= context=Intern-ISDN callgroup=1 devices=6 /etc/capi.conf #SuSEconfig.isdn generated # card file proto io irq mem ca...

...fig allowed me to have multiple MSN's on the same ISDN/Fritz! card under seperate contexts. ------------------------------------------------------------------ [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.4 echocancel=yes ; [interfaces] context=work_incoming msn=123456 incomingmsn=123456 controller=1 softdtmf=1 accountcode= devices=2 ; context=pers_incoming msn=654321 incomingmsn=654321 controller=1 softdtmf=1 accountcode= devices=2 ------------------------------------------------------------------------ ------------ No matter how hard I try using the new syntax, I can'...

...f the other numbers) I don't get CLID at all. Any ideas? ; use 0703241432 as outgoing msn exten => _070.,1,Dial(CAPI/@0703241432:${EXTEN}|30|r) in capi.conf I have: [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 ;rxgain=0.0 ;txgain=0.0 [interfaces] msn=0703241432 incomingmsn=703241432 controller=1,2 softdtmf=1 accountcode= context=default ;echosquelch=1 echocancel=yes echotail=64 ;deflect=12345678 devices=2 msn=0703241434 incomingmsn=703241434 controller=1,2 softdtmf=1 accountcode= context=default ;echosquelch=1 echocancel=yes echotail=64 ;deflect=12345678 devices=2...

...default', but no invalid handler -- DISCONNECT_IND ID=002 #0x0a68 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason = 0x3400 Now I do have a capi_conf file that in my opinion should send inbound calls to a different context: [interfaces] msn=0221591030 incomingmsn=221591030 controller=1 devices=2 softdtmf=1 callgroup=1 context=from-chan_capi Can anybody help me understanding if the incoming call gets answered and if so why it is sent to a default context? What is an invalid handler? Thanks in adavance Aldo

...,3,Dial(CAPI/g1/${EXTEN:1}/b) exten => _9.,4,Congestion /etc/capi.conf contains : c2 c2.bin DSS1 - - - - P2P c2 c2.bin DSS1 - - - - P2P /etc/asterisk/capi.conf contains : [general] nationalprefix=0 internationalprefix=00 rxgain=0.9 txgain=0.3 ; interface sections ... [ISDN1] isdnmode=DID incomingmsn=* controller=1 group=1 softdtmf=on relaxdtmf=on accountcode= context=capi-in holdtype=hold echocancel=yes echotail=64 bridge=yes callgroup=1 devices=2 [ISDN2] isdnmode=DID incomingmsn=* controller=2 group=1 softdtmf=on relaxdtmf=on accountcode= context=capi-in holdtype=hold echocancel=yes echotai...

Hi, I'm currently using chan_capi-cm-0.6, with the following capi.conf: [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 language=de [ISDN1] msn=8304490 incomingmsn=8304490 isdnmode=msn group=1 controller=1 softdtmf=1 context=demo echosquelch=1 echocancel=yes echotail=64 callgroup=1 devices=2 Each user has a different numer, e.g. 83044910, 83044911, 83044912 and so on. This number should appear on the display of the called party, but how do I configure this?...

Hi chan_capi users, this thing is awesome, no delays like in modem_i4l! Plus, it got those nice ISDN features. Here's my question: Does my service provider (Deutsche Telekom) have to provide me with these Services (CD, ECT)? (the Readme in 0.2.5 says "does not relay on service CD") I know, that I don't have CFU,CFNR,CFBS (which I would have to order seperately). How likely

...ial numbers as Caller ID when dialing out. > > Configration: > capi.conf > --------- > > [general] > nationalprefix=0 > internationalprefix=00 > rxgain=0.8 > txgain=0.8 > > [interfaces] > mode=immediate > isdnmode=ptp > msn=BAAAAAA > incomingmsn=* > controller=1 > softdtmf=1 > accountcode= > context=main-menu > usecallerid=yes > callerid=asreceived > ;echosquelch=1 > ;echocancel=yes > ;echotail=64 > callgroup=1 > pickupgroup=1 > devices=2 > > mode=immediate > isdnmode=ptp > m...

...ncoming-isdn driver=i4l language=en type=autodetect ;This I'm doing directly in the extension.conf ;stripmsd=1 dialtype=tone ;dialtype=pulse ;mode=answer ;mode=ring mode=immediate ; ISDN example group=1 ;registered one number. msn=4625xxxx ;accepting several more. Could have used * as well ;incomingmsn=57966,57881,57882,57883,57884,57885,57886,57887 incomingmsn=4625xxxx device => /dev/ttyI0 device => /dev/ttyI1

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/bmp Size: 2918 bytes Desc: Picture (Metafile) Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050307/cb404791/attachment.bmp

...es Armin has been adding in chan_capi. The capi.conf format has changed, so my question is how do I define a deflect= statement for different incoming MSN's? I've tried to define a section for each (group of) MSN with a different "deflect". Is that correct? [DIVA1] isdnmode=msn incomingmsn=146472130 controller=1 group=5 accountcode=diva context=default deflect=0612110618 devices=2 [DIVA2] isdnmode=msn controller=1 group=5 incomingmsn=146472131,146472132,146472133,146472134,146472136 accountcode=diva context=default deflect=0187174173 devices=2 [DIVA3] isdnmode=msn controller=1 grou...

Hi, I try to use ISDN4Linux drivers with Asterisk. In modem.conf i put /dev/ttyIO. Everything is OK when i lauch asterisk but, when i call Asterisk nothing happen. Someone can help me ? Rattana -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20030407/13e78d8e/attachment.htm

...if it was possible for asterisk to ignore certain MSNs. I have a AVM Fritz/BRI with two MSNs: 7770001 and 7770002. I would like asterisk (with chan_capi) to ignore 7770001 such that a regular phone on the bus will ring; calls for 7770002 should be picked up by asterisk. I configured msn=7770002 incomingmsn=* within capi.conf and figured this would do the trick, but asterisk picks everything up on the bus. I'm I missing something? thanks, andre

Hello, I am using chan_capi and would like * to behave differently depending on the MSN the caller dials. Is there a way to route incoming ISDN calls to different contexts based on the MSN dailled? I have tried something like msn=1234 incomingmsn=1234 context=msn1 msn=4567 incomingmsn=4567 context=msn2 in capi.conf but with no results. Thanks for any hints. -Walter -- Walter Doerr =*= wd@infodn.rmi.de =*= FAX: +49 2421 962001 "The poor folks who only have 100MBytes of RAM five years from now may not be...

...Asterisk-box there are 2 Fritzcards (module for second card compiled with changes on sourcecode found in the web). "capi info" shows: Contr1: 2 B channels total, 2 B channels free. Contr2: 2 B channels total, 2 B channels free. Here a snipplet of my capi.conf: [interfaces] msn=7501,7502 incomingmsn=* controller=1,2 devices=2,2 Is that correct? I also tried "devices=4". When I try to make 3 simultaneous connections from SIP to ISDN the first and second one works, but on the third connection this happens: -- Executing Dial("SIP/gunnar-26ea", "CAPI/7501:7986:bBYEXTENSIO...