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
I don't know about SNOM, but with Xlite Softphone you can have the SoftPhone internal dialplan. Ex. [29]xxxxxxxx;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 9XXXXXXXX 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 <lists@wildgooses.com> 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 >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070123/bc34a584/attachment.htm
Gordon Henderson
2007-Jan-23 05:20 UTC
[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 9999) 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
Steve Murphy
2007-Jan-23 07:20 UTC
[asterisk-users] Re: Dial plan constructions suggestions?
On Tue, 2007-01-23 at 06:11 -0700, Ed W <lists@wildgooses.com> 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).I had the same situation, in that I wanted to be able to use the Voicemail 'dial back' feature, and had a few phones with internal CID-based dial features, that I wanted to be allowed to be used. Your normal context is set up to operate with a '9' (or whatever) in front; so it is clear that you will need a different context from which to dial, a context that doesn't have the '9' at the beginning. For voicemail, the solution is simple; you create a context much like your normal outgoing context, except, without the '9' in front. Then, in voicemail.conf, you make use of: ; dialout=fromvm ; Context to dial out from [option 4 ; from the advanced menu] ; if not listed, dialing out will not be permitted ; callback=fromvm ; Context to call back from ; if not listed, calling the sender back will not ; be permitted by declaring your mailbox as so: 80 => 5555,Alex Murphy,,,callback=fromvmhome|dialout=fromvmhome| saycid=yes|tz=mountain|review=yes (stupid mail package folds lines!) --- For those phones with a CID list of their own, and autodialers, you merely associate them with a context that allows that... in zapata.conf, you might set up: context = fromSeanUniden callerid="UnidenPowerMax2.4Ghz"<5> channel => 5 Or whatever's appropriate for your setup. The main idea is to set the 'context' so something special for that phone. --- hope this helps...! murf -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3239 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070123/6940aba0/smime.bin