search for: incomingpstn

...does something [createconf] ;does something ;outgoing calls ? main purpose of onecontext exten => _X.,1,Dial(SIP/${EXTEN}@provider-out) exten => _X.,2,Hangup [default] ;mailbox for 2092 and other users Now this is where the problems start! For incoming calls I tried to do ?include => incomingpstn? in ?onecontext? which I thought would call a new context called ?incomingpstn? which would have an entry for the dummy user. i.e. [incomingpstn] exten => 2093,1,Wait(1) exten => 2093,n,Background(MainMenu) exten => 1,1,Goto(InternalExtension,2093,1) //directs to another context calle...

Just another bit of info which might help solve this: Looking at the Asterisk log messages - I notice when I start up Asterisk, I see the error: pbx_config.c: Can't use 'next' priority on the first entry! Could I be right that its something got to do with priorities? I changed the incomingpstn context to the following eliminating the 'n' field and still the same errors were display in the log file on startup and it didn't allow me to interrupt the menu. [incomingpstn] exten => s,1,Wait(1) exten => s,2,Background(MainMenu) ;exten => s,3,WaitExten(10) exten => 1,1,...

...email etc My provider told me to change my sip.conf as follows register => username:password@sip.blueface.ie/2093 ; To receive incoming calls specify this block and replace "yourcontext" for your dial plan. [blueface-in] type=peer host=sip.blueface.ie context=incomingpstn And then in my extensions.conf to have something similar to the following (or however I wanted to handle my incoming calls) [incomingpstn] exten => 2093,1,Wait(1) exten => 2093,n,Background(MainMenu) exten => 1,1,Goto(InternalExtension,2093,1) //press 1 for internal...

...33 insecure=very registerattempts=0 ;context=default register => username@providerIP/1234 ;To make outgoing calls specify this block [providerIP] type=peer user=phone host=providerIP port=6060 fromdomain=providerIP fromuser=username secret=password username=username insecure=very context=incomingpstn authname=username allow=gsm allow=ulaw allow=alaw ;allow=g729 ;NBNB This is where the issue is [314] type=friend username=314 canreinvite=no context=from-provider insecure=very host=dynamic nat=yes dtmfmode=rfc2833 mailbox=314 disallow=all allow=alaw allow=ulaw allow=g723....

...e=us zapata.conf [channels] signalling=fxo_ks echocancel=yes echocancelwhenbridged=yes usecallerid=yes context=outstation channel=> 1-4 signalling=fxs_ks echocancel=yes echocancelwhenbridged=yes usecallerid=yes group=2 context=incomingpstn channel=> 5-16 Best regards, Duane Pudenz Network Infrastructure Manager Shasta Industries -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060219/d5fc3f7b/attachment.htm

Dears; The problem was related to something else. The Digium card has two PRI ports, actually to get it UP, I have to configure the two ports and both of those two ports to take the timing from span 1. Why this, I do not know ! Although I am using only one E1 connected to span 1, so why I have to configure the other span !! After configuring the second span, so now one D channel for span 1 is

...working fine, and suddenly I start getting the below: sig_pri.c:985 pri_find_dchan: Span 1: No D-chanannel anyway! There is a Yellow Alarm, so what it could be the problem? My configuration as following: system.conf span=1,1,0,ccs,hdb3,yellow bchan=1-15,17-31 dchan=16 chan_dahi.conf context=IncomingPSTN group=0 signalling=pri_cpe switchtype=euroisdn channel=>1-15,17-31 What it could be? How can I check if the problem from the port it self? Or from the provider? Regards Bilal

...dahdi_enable_ec: Unable to enable echo cancellation on channel 1 (No such device) What could be the reason? The asterisk version is Asterisk 1.8.5.0 DAHDI Version: 2.4.1.2 Echo Canceller At the system.conf I have the following: echocanceller=mg2,1-16 fxoks=1-16 At the chan_dahdi.conf context=IncomingPSTN signalling=fxs_ks rxgain=0.0 txgain=0.0 channel => 1-16 group=1 channel => 1-16 The calls are working, but the echo is appearing. Something strange is the result of the dahd_cfg, but really if I changed the configuration in the system.conf and I made it fxs instead of fxo, then it is not wo...

Hi All; To overcome the echo problem, what mainly I have to do in the configuration other than the following line in the system.conf under dahdi directory? echocanceller=mg2,1-16 1) How can I know if the digium card supporting echo cancellator? 2) If I am getting a message in the consol that unable to enable the echo cancelator, then what does it means? The hardware is not supporting echo