[asterisk-users] SIP 484 (Early Dial) and International Dialing

James FitzGibbon james.fitzgibbon at gmail.com
Mon Apr 2 13:21:05 MST 2007


I'm building a dialplan for use with a bunch of GXP2000 desk sets.  During
testing, we had some user issues surrounding the lack of an on-phone
dialplan.  Users would hit 9 and sit there waiting for a redial tone, and
the GXP would time out, sending just '9' to *, which couldn't do much other
than spit back a 404 or play pbx-invalid.

I turned on the "early dial" option on the GXP, which causes each digit to
be sent as it is pressed, and the user response was much more favourable.
Now I come to set up my international dialplans and I'm running into a
problem.

The textbook dial pattern for international calls:

_9011.

Isn't working because * matches the first digit after 011 and sends an
incomplete dialstring (dialing something like Zap/R1/0119 for example).

I've tried using patterns with multiple . wildcards, and switching from . to
X, putting patterns like

_9011XXX
_9011XX
_9011X

In the hopes that * would see that "90119" could potentially match a longer
extension and not match immediately.  No luck though - dialing still starts
immediately when one digit past 011 is received.

Any thoughts on how to get around this?  Right now the best I have (and
that's not saying much) is to have something like:

[initialcontext]
exten => _9011,1,DISA(no-password|somecontext)

[somecontext]
exten => _X.,1,Dial(Zap/R1/011${EXTEN})

But that's ugly, not to mention confusing to the users because the amplitude
of the dialtone generated by the GXP is lower than the dialtone generated by
*, so they notice the bump when they've dialed 9011.

Any suggestions appreciated.

-- 
j.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070402/0d0945f5/attachment.htm


More information about the asterisk-users mailing list