I've been running into an issue with my Polycom 501 and Asterisk. I realized, after much mucking around, that when I dial a number (and press the send key) that is invalid , but could still match an Asterisk pattern (example: I dial 567, which is not a valid extension, but my diaplan accepts _567XXXX as a pattern) instead of sending the call as is and ultimately failing, the phone is "intelligent enough" to sit and wait for extra digits in case I meant to dial 567111. Now thats a problem for me. How can I make Asterisk (or the 501) treat the attempted extension 567 as a valid try and let Asterisk handle the error ?(instead of the phone trying to do what it think is best and handling the error on it's own). Is there an Asterisk setting for that? Failing that, is there a Polycom setting to disable this "intelligent" error handling? Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060908/6e9a2f68/attachment.htm
With SIP, asterisk processes the digits it receives in the invite from the Polycom. There is no communication of dialplan information in SIP. The polycom should send the digits as soon as you press dial. You can program the polycom with a dialplan that will tell it when to send the digits, but that only works if you dial off-hook. I like on hook dialling, since it sends what i tell it, when I tell it. This should never happen when you press dial - it should try right away. My 301 does this, maybe they changed something in the newer firmware? -Tim On September 8, 2006 14:33, Mike wrote:> I've been running into an issue with my Polycom 501 and Asterisk. > > I realized, after much mucking around, that when I dial a number (and press > the send key) that is invalid , but could still match an Asterisk pattern > (example: I dial 567, which is not a valid extension, but my diaplan > accepts _567XXXX as a pattern) instead of sending the call as is and > ultimately failing, the phone is "intelligent enough" to sit and wait for > extra digits in case I meant to dial 567111. > > Now thats a problem for me. How can I make Asterisk (or the 501) treat the > attempted extension 567 as a valid try and let Asterisk handle the error > ?(instead of the phone trying to do what it think is best and handling the > error on it's own). > > Is there an Asterisk setting for that? > Failing that, is there a Polycom setting to disable this "intelligent" > error handling? > > > Mike-- Tim St. Pierre IP telephony specialist sip://5101@communicatefreely.net Toronto: 647 722 6930 Toll-Free 1 888 488 6940 tim@communicatefreely.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20060908/55fb4280/attachment.pgp
Mike wrote:> I've been running into an issue with my Polycom 501 and Asterisk. > > I realized, after much mucking around, that when I dial a number (and press > the send key) that is invalid , but could still match an Asterisk pattern > (example: I dial 567, which is not a valid extension, but my diaplan accepts > _567XXXX as a pattern) instead of sending the call as is and ultimately > failing, the phone is "intelligent enough" to sit and wait for extra digits > in case I meant to dial 567111. > > Now thats a problem for me. How can I make Asterisk (or the 501) treat the > attempted extension 567 as a valid try and let Asterisk handle the error > ?(instead of the phone trying to do what it think is best and handling the > error on it's own). > > Is there an Asterisk setting for that? > Failing that, is there a Polycom setting to disable this "intelligent" error > handling? > > > MikeYou want to look at the dialplan section in your sip config file or on the device's web config. Specifically the dialplan.digitmap and dialplan.impossibleMatchHandling settings. (These are explained in detail in the Admin Guide available on polycom's website). If you don't want the phone to do any dial plan matching you should make the digitmap accept any dial string (ie ".") and set your timeouts appropriately. -Dave