For those interested I built a very simple dial plan for voipms including
fax-rx from David (Thanks David) and black list db. Its very simple and
generic and might work for many providers.
There is another portion of the fax-rx which is a script that David created
that "monitors" for the fax file to be created so it can be converted and
emailed.

The "sit" sound file can be download it of the net or you can email me and
ill send it to you.



[trunk-provider]
include => voipms-inbound
include => voipms-outbound

[voipms-outbound]
exten => _1NXXNXXXXXX,1,Set(CALLERID(name)=Your Name)
exten => _1NXXNXXXXXX,n,Set(CALLERID(num)=YOURDID)
exten => _1NXXNXXXXXX,n,Dial(SIP/${EXTEN}@voipms)
exten => _1NXXNXXXXXX,n,Hangup()
exten => _NXXNXXXXXX,1,Set(CALLERID(name)=Your Name)
exten => _NXXNXXXXXX,n,Set(CALLERID(num)=YOURDID)
exten => _NXXNXXXXXX,n,Dial(SIP/${EXTEN}@voipms)
exten => _NXXNXXXXXX,n,Hangup()
exten => _011.,1,Dial(SIP/${EXTEN}@voipms)
exten => _011.,n,Hangup()
exten => _00.,1,Dial(SIP/${EXTEN}@voipms)
exten => _00.,n,Hangup()

[voipms-inbound]
exten => YOURDIDHERE,1,GotoIf($[${BLACKLIST()}]?blacklist,1)
exten => YOURDIDHERE,n,Dial(SIP/1003,20)
exten => YOURDIDHERE,n,Voicemail(4222@default,u)

exten => YOURDIDHERE,1,Goto(fax-rx,fax,1)

exten => blacklist,1,Zapateller
exten => blacklist,n,Playback(sit)
exten => blacklist,n,Playback(ss-noservice)
exten => blacklist,n,Hangup


[fax-rx]
exten = s,1,NoOp(Receive FAX)
exten =
s,n,Set(emailaddr=${IF(${DB_EXISTS(actionlist/fax${CALLERID(dnid)})}?${DB_RESULT}:${DB(actionlist/fax)})})
exten =
s,n,Set(FAXFILE=/tmp/fax~${CALLERID(NUM)}~${emailaddr}~${FILTER(0123456789,${UNIQUEID})})
exten = s,n,Set(LOCALHEADERINFO=Your Name)
exten = s,n,Set(LOCALSTATIONID=Your Name)
exten = s,n,ReceiveFAX(${FAXFILE}.tiff)
exten = s,n,Log(NOTICE,New FAX: ${FAXPAGES} page(s) from ${CALLERID(NUM)}
(${REMOTESTATIONID}) to ${CALLERID(dnid)})
exten = s,n,Hangup()
exten = s,n,Return()

On Mon, Oct 3, 2011 at 4:28 PM, Tom Mazzotta <tmazzo...@titanmicro.com>wrote:

> You need to modify extensions.conf. ****
>
> ** **
>
> See example here: http://lonnie.abelbeck.com/astlinux/info/webgui.php****
>
> ** **
>
> *From:* Fernando Fuentes [mailto:digitaldis...@gmail.com]
> *Sent:* Monday, October 03, 2011 5:25 PM
> *To:* AstLinux Users Mailing List
> *Subject:* [Astlinux-users] BackList option****
>
> ** **
>
> I was wondering if anybody was using the blacklist option?****
>
> I have generated a DB under the blacklist tab but I am not sure how to
> actually make the blacklist work.****
>
> For some reason I thought that I could generate the list and they would get
> blocked base on that list without having to make any modifications to my
> conf files.****
>
> I am only asking because calls are still coming in.****
>
> ** **
>
> Thank You!****
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to