asterisk users - Aug 2006 - *****SPAM***** Is there a smarter way to ban expensive calls in dial plan?

Software zur Erkennung von "Spam" auf dem Rechner

    priamus.teamware-gmbh.de

hat die eingegangene E-mail als m?gliche "Spam"-Nachricht
identifiziert.
Die urspr?ngliche Nachricht wurde an diesen Bericht angeh?ngt, so dass
Sie sie anschauen k?nnen (falls es doch eine legitime E-Mail ist) oder
?hnliche unerw?nschte Nachrichten in Zukunft markieren k?nnen.
Bei Fragen zu diesem Vorgang wenden Sie sich bitte an

    postmaster@teamware-gmbh.de

Vorschau: Hi List, I need a bit of advice please. I want to ban
  calls to expensive destinations such as cell phones. This is fairly
  simple here in the UK because all cell phone numbers begin with a 7
  where as all geographic numbers begin 1 and 2 [...] 

Inhaltsanalyse im Detail:   (5.7 Punkte, 5.0 ben?tigt)

Pkte Regelname              Beschreibung
---- ---------------------- --------------------------------------------------
 0.1 FORGED_RCVD_HELO       "Received"-Kopfzeilen enthalten gef?lschte
                            HELO-Identifikation
-2.6 BAYES_00               BODY: Spamwahrscheinlichkeit nach Bayes-Test: 0-1%
                            [score: 0.0000]
 0.0 HTML_MESSAGE           BODY: Nachricht enth?lt HTML
 2.2 DCC_CHECK              Gelistet im DCC-System
                            (http://rhyolite.com/anti-spam/dcc/)
 1.7 MSGID_DOLLARS          Muster in Kopfzeile "Message-ID" typisch
f?r Spam
 1.9 RATWARE_MS_HASH        Bulk email fingerprint (msgid ms hash) found
 2.8 RATWARE_OUTLOOK_NONAME Bulk email fingerprint (Outlook no name)
                            found
-0.4 AWL                    AWL: From: address is in the auto white-list

Die urspr?ngliche Nachricht enthielt nicht ausschlie?lich Klartext
(plain text) und kann eventuell eine Gefahr f?r einige E-Mail-Programme
darstellen (falls sie z.B. einen Computervirus enth?lt).
M?chten Sie die Nachricht dennoch ansehen, ist es wahrscheinlich
sicherer, sie zuerst in einer Datei zu speichern und diese Datei danach
mit einem Texteditor zu ?ffnen.

-------------- next part --------------
An embedded message was scrubbed...
From: "Chris Blunt" <chris.blunt@entropy-it.com>
Subject: [asterisk-users] Is there a smarter way to ban expensive calls in
	dial plan?
Date: Tue, 1 Aug 2006 15:16:04 +0100
Size: 13329
Url:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060801/c141f780/attachment.eml

Insert your patterns in a database, have a field called expensive, and query
your database before making a call!

On 8/1/06, Chris Blunt <chris.blunt@entropy-it.com>
wrote:
>
>  Hi List,
>
>
>
> I need a bit of advice please.  I want to ban calls to expensive
> destinations such as cell phones.
>
>
>
> This is fairly simple here in the UK because all cell phone numbers begin
> with a 7 where as all geographic numbers begin 1 and 2
>
>
>
> Elsewhere this is different, take Andorra for example all numbers begin
> 376, cell phone numbers are 3763, 3764 and 3765
>
>
>
> So if I try the following dial plan my pattern always matches the first
> wild card
>
>
>
> Exten => _00376.,1,Dial(my iax terminiator)
>
> Exten => _003763.,1,Congestion
>
> Exten => _003764.,1,Congestion
>
> Exten => _003765.,1,Congestion
>
>
>
> I seem to have been able to fix this with adding an x after the 6 in the
> first extension to make the patterns all the same length and thus making a
> better match with the blocked numbers.
>
>
>
> Example:
>
>
>
> Exten => _00376x.,1,Dial(my iax terminiator)
>
> Exten => _003763.,1,Congestion
>
> Exten => _003764.,1,Congestion
>
> Exten => _003765.,1,Congestion
>
>
>
>
>
> This is just so long winded, and you can imagine doing this for a huge
> list of destinations.
>
>
>
> If any one can suggest an improved or more efficient way of doing this, I
> would be greatly appreciated!
>
>
>
> Best regards
>
>
>
> Chris
>
>
>
> --
>
>
>
> Chris Blunt
>
> Entropy IT Ltd
>
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>

-- 
Com os melhores cumprimentos,

Marco Mouta
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060801/6f2c2ec2/attachment.htm

Hi, 

try to list the blocked numbers first! 
Then you should be able to use wildcards without a problem. :-) 
That was the solution for the same problem at our dialplan. 

hth 
Martin 

  ----- Original Message ----- 
  From: Chris Blunt 
  To: asterisk-users@lists.digium.com 
  Sent: Tuesday, August 01, 2006 4:16 PM
  Subject: [asterisk-users] Is there a smarter way to ban expensive calls indial
plan?


  Hi List, 

   

  I need a bit of advice please.  I want to ban calls to expensive destinations
such as cell phones.

   

  This is fairly simple here in the UK because all cell phone numbers begin with
a 7 where as all geographic numbers begin 1 and 2

   

  Elsewhere this is different, take Andorra for example all numbers begin 376,
cell phone numbers are 3763, 3764 and 3765

   

  So if I try the following dial plan my pattern always matches the first wild
card

   

  Exten => _00376.,1,Dial(my iax terminiator) 

  Exten => _003763.,1,Congestion 

  Exten => _003764.,1,Congestion 

  Exten => _003765.,1,Congestion

   

  I seem to have been able to fix this with adding an x after the 6 in the first
extension to make the patterns all the same length and thus making a better
match with the blocked numbers.

   

  Example: 

   

  Exten => _00376x.,1,Dial(my iax terminiator) 

  Exten => _003763.,1,Congestion 

  Exten => _003764.,1,Congestion 

  Exten => _003765.,1,Congestion

   

   

  This is just so long winded, and you can imagine doing this for a huge list of
destinations.

   

  If any one can suggest an improved or more efficient way of doing this, I
would be greatly appreciated!

   

  Best regards

   

  Chris 

   

  --

   

  Chris Blunt

  Entropy IT Ltd

   



------------------------------------------------------------------------------


  _______________________________________________
  --Bandwidth and Colocation provided by Easynews.com --

  asterisk-users mailing list
  To UNSUBSCRIBE or update options visit:
     http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060801/10fe659b/attachment.htm

Ciao Chris,
> So if I try the following dial plan my pattern always matches the
> first wild card
> 
> Exten => _00376.,1,Dial(my iax terminiator) 
> Exten => _003763.,1,Congestion 
> Exten => _003764.,1,Congestion 
> Exten => _003765.,1,Congestion
This is a common pitfall in Asterisk dialplans: Asterisk doesn't try to
match your extensions in the order you insert them into your dialplan,
but it sorts them out according to its own internal order.

See the CLI command "show dialplan example" to discover how it sorts
them.

So, how to solve this misunderstanding?

You must create other contexts, and include them in your main context.
Asterisk will try to match current context's extensions first, and then
extensions included from other contexts, in the order you included them.

Please refer to
http://www.voip-info.org/wiki/index.php?page=Asterisk+config+extensions.conf+sorting
for further information.

HTH,

-- 
Andrea Spadaccini
Multimedia Technologies Institute s.r.l.