[asterisk-users] Dial plan constructions suggestions?
Can I ask for some advice on dial-plan construction please I have setup my dialplan to use 9 to get a zap trunk, leaving everything else for internal extensions. However, this creates a problem in that my callerid is correct, but doesn't work to re-dial the incoming caller. So if I simply click missed calls on my Snom phone and hit redial then it tries to dial an internal extension. So I then setup Asterisk to add a 9 to the incoming callerid for all calls which come via the Zap trunk, but now this creates some issues with applications like Snapanumber and perhaps HudLite, which are trying to map the caller ID to numbers in the addressbook (and I don't really want my internal Outlook address books to have everyone listed with a 9 in front of their number) How are others handling this? I have considered simply dropping the prefix digit and working around any clashes in internal and external numbers (not very hard). Grateful for any thoughts Ed W ___ --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
Re: [asterisk-users] Dial plan constructions suggestions?
I don't know about SNOM, but with Xlite Softphone you can have the SoftPhone internal dialplan. Ex. [29];match=1;pre=0; this adds a Zero to every nine digits number s I dial begining with 2 or 9 , this has nothing to do with asterisk, is VoiP phone dialplan. So you can tell to the softphone that when you dial a specific pattern like 9 the Softphone should add an extra 9 in the beginning. This helped me out to import all my contacts from Outlook without having to Add a 0 in the begining of all of them. Hope this help On 1/23/07, Ed W [EMAIL PROTECTED] wrote: Can I ask for some advice on dial-plan construction please I have setup my dialplan to use 9 to get a zap trunk, leaving everything else for internal extensions. However, this creates a problem in that my callerid is correct, but doesn't work to re-dial the incoming caller. So if I simply click missed calls on my Snom phone and hit redial then it tries to dial an internal extension. So I then setup Asterisk to add a 9 to the incoming callerid for all calls which come via the Zap trunk, but now this creates some issues with applications like Snapanumber and perhaps HudLite, which are trying to map the caller ID to numbers in the addressbook (and I don't really want my internal Outlook address books to have everyone listed with a 9 in front of their number) How are others handling this? I have considered simply dropping the prefix digit and working around any clashes in internal and external numbers (not very hard). Grateful for any thoughts Ed W ___ --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 ___ --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
Re: [asterisk-users] Dial plan constructions suggestions?
On Tue, 23 Jan 2007, Ed W wrote: Can I ask for some advice on dial-plan construction please I have setup my dialplan to use 9 to get a zap trunk, leaving everything else for internal extensions. However, this creates a problem in that my callerid is correct, but doesn't work to re-dial the incoming caller. So if I simply click missed calls on my Snom phone and hit redial then it tries to dial an internal extension. So I then setup Asterisk to add a 9 to the incoming callerid for all calls which come via the Zap trunk, but now this creates some issues with applications like Snapanumber and perhaps HudLite, which are trying to map the caller ID to numbers in the addressbook (and I don't really want my internal Outlook address books to have everyone listed with a 9 in front of their number) How are others handling this? There was a thread about this not too long ago, so the archives may have a bit more on it... The way I handle it is by forcing the caller to dial the full number starting with zero (normally 10 or 11 digits in the UK - which I'm guessing you're from too) Zero is the new 9 ;-) This mimics the way mobile phones work here too where you need to dial the full number with the leading zero, even if you'd think it's a local call. Incoming caller-id always provides you with the full 10 or 11 digit number with the zero (or with the country code prefix when that works) The ability to dial the full number in the UK has been avalable for some years now... In my dialplan I look for a leading zero, and when I see one, after premissions checks, etc. I just route the outgoing call with the zero to the relevant zap device. I just tell my clients that they now have to dial the full number including STD code - just like they do on their mobiles. I still provide a traditional '9' for an outside line though - there are a few numbers in the UK that don't start with a leading 0 - 'operator' (100), directory enquriries (118xxx) and a few others for reporting faults, last number dialled and so on. So if they like they can dial 9 then the 5 or 6 digit local number, or just dial 0 for everything. Don't forget to add rules for 999 (and ) to force out-dialling to 999 via a Zap line... And I guess you could eliminate the leading 9 too, if you had explicit entries in the dialplan for these non-zero numbers (or to deny them!) Gordon ___ --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
Re: [asterisk-users] Dial plan constructions suggestions?
Hi There was a thread about this not too long ago, so the archives may have a bit more on it... The way I handle it is by forcing the caller to dial the full number starting with zero (normally 10 or 11 digits in the UK - which I'm guessing you're from too) Yes, I use something similar on another box, but there I support shorter dial codes as well. It's not to hard to make 8 dial 0208 or 7 dial 0207, etc. I happen to also map some of the 1xx codes across as well. It's still not a complete solution though because on this other box I have a business line and a personal line and I send calls to different lines based on the type of call (or more usually the time of day...). I want to have seperate billing basically. When the call comes in it makes sense to have the caller tagged with (in my dialplan) 9 for a personal call, and I use 3 (for no good reason) for my business line. I actually have one phone which defaults to business line if I don't add a prefix, another DECT phone which is my personal phone, but I can see on either where the call is coming from and also force the call to use a different route just by dialing the prefix. Basically it's tricky. I do already use custom ring tones for each line, so I guess I could drop the prefix, but it's nice to have it so that I can see at a glance whether it's a business call or not... Any other suggestions? Any suggestions on other software than Snap which does callerId lookup from Thunderbird (not Outlook). For example is HUDLite ever going to support Thunderbird...? Cheers Ed W ___ --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
