VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
mwatson at becon.org Guest
|
Posted: Wed May 28, 2008 11:18 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Might want to do a "sip set debug peer <peer id>"
You should then be able to see the sip packet dumps that are going between the phone and *. Might give you some clues.
--
Matt
http://www.mattgwatson.ca
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Henrik Ostergaard Madsen
Sent: Wednesday, May 28, 2008 12:54 PM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Calling '**1' through Asterisk
I am experiencing problems calling '**1' through astrisk from an VOIP
telephone. Asterisk appearently does not accept the call and never show
any indication of an incoming call (using asterisk -rvvvvvvvvvvvvvvvvvv).
On the phone, I get an immideate 'Call ended'. This occurs on both an
Linksysy SPA941 and an LIP TA100. The same happens with '**'
Using '**11' or '*1' or '*11' instead, the call gets right through..
I can see on tcpdump that the SIP packages does reach the asterisk server
and gets answered.
Does anyone have a clue on what is going on?
Regards
Henrik
-----------------------------------------------------------
Henrik ?stergaard Madsen Phone: +45 44 48 44 92
PhD, M.Sc. Cell: +45 30 94 02 88
Mosegard Park 42 email: Henrik at Ostergaard.net
DK-3500 V?rl?se WWW homepage:
Denmark http://www.Ostergaard.net/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
Back to top |
|
|
Henrik at ostergaard.net Guest
|
Posted: Wed May 28, 2008 11:53 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
I am experiencing problems calling '**1' through astrisk from an VOIP
telephone. Asterisk appearently does not accept the call and never show
any indication of an incoming call (using asterisk -rvvvvvvvvvvvvvvvvvv).
On the phone, I get an immideate 'Call ended'. This occurs on both an
Linksysy SPA941 and an LIP TA100. The same happens with '**'
Using '**11' or '*1' or '*11' instead, the call gets right through..
I can see on tcpdump that the SIP packages does reach the asterisk server
and gets answered.
Does anyone have a clue on what is going on?
Regards
Henrik
-----------------------------------------------------------
Henrik ?stergaard Madsen Phone: +45 44 48 44 92
PhD, M.Sc. Cell: +45 30 94 02 88
Mosegard Park 42 email: Henrik at Ostergaard.net
DK-3500 V?rl?se WWW homepage:
Denmark http://www.Ostergaard.net/Henrik |
|
Back to top |
|
|
brent at texascountryt... Guest
|
Posted: Wed May 28, 2008 11:58 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Check your features.conf file and make sure that combination or a
similar combination (*1 or ** ) for instance isn't defined in there for
some reason.
Matt Watson wrote:
Quote: | Might want to do a "sip set debug peer <peer id>"
You should then be able to see the sip packet dumps that are going between the phone and *. Might give you some clues.
--
Matt
http://www.mattgwatson.ca
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Henrik Ostergaard Madsen
Sent: Wednesday, May 28, 2008 12:54 PM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Calling '**1' through Asterisk
I am experiencing problems calling '**1' through astrisk from an VOIP
telephone. Asterisk appearently does not accept the call and never show
any indication of an incoming call (using asterisk -rvvvvvvvvvvvvvvvvvv).
On the phone, I get an immideate 'Call ended'. This occurs on both an
Linksysy SPA941 and an LIP TA100. The same happens with '**'
Using '**11' or '*1' or '*11' instead, the call gets right through..
I can see on tcpdump that the SIP packages does reach the asterisk server
and gets answered.
Does anyone have a clue on what is going on?
Regards
Henrik
-----------------------------------------------------------
Henrik ?stergaard Madsen Phone: +45 44 48 44 92
PhD, M.Sc. Cell: +45 30 94 02 88
Mosegard Park 42 email: Henrik at Ostergaard.net
DK-3500 V?rl?se WWW homepage:
Denmark http://www.Ostergaard.net/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
|
|
Back to top |
|
|
rizwanhasham at gmail.com Guest
|
Posted: Thu May 29, 2008 6:15 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
seems like asterisk could not find the extension number "**1". does your
context "from-internal" have this extensions? if not then create one or
include the context which contains the extension **1 in from-internal and
then try.
On Thu, May 29, 2008 at 1:10 AM, Henrik Ostergaard Madsen <
Henrik at ostergaard.net> wrote:
Quote: | Thanks for the reply.
Good point with the features.conf. But I do not have any features.conf
which conflict with **1 - and it is **2, **3 etc as well. Anyway, **10
should be
tricked by features as well, which it does not. And features only works on
a
bridged call, and this does not even get that far..
The sip set debug peer <> did get me some extra output, but I am not able
to get any sense from it. This is what came out (Asterisk is on
192.168.2.1
AND 192.168.27.7 and the vopiphone is on 192.168.7.98 and has the
username 018):
<--- SIP read from 192.168.27.98:5060 --->
INVITE sip:**1 at 192.168.2.1 SIP/2.0
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.27.98:5060;rport;branch=z9hG4bK-16ba5-
58c7d35-4a11b393
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER,
SUBSCRIBE, NOTIFY, MESSAGE, INFO
User-Agent: ATMEL_UA v0.0.25-alpha
Max-Forwards: 70
Contact: <sip:018 at 192.168.27.98:5060>
Content-Type: application/sdp
Content-Length: 334
v=0
o=018 12119074 77112119074177 IN IP4 192.168.27.98
s=audio
c=IN IP4 192.168.27.98
t=0 0
m=audio 16426 RTP/AVP 0 8 18 4 97 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16
a=ptime:30
<------------->
--- (12 headers 15 lines) ---
Sending to 192.168.27.98 : 5060 (NAT)
Using INVITE request as basis request - 10b2f2f0-621ba8c0-13c4-40030-
16ba5-2f6d4897-16ba5
<--- Reliably Transmitting (no NAT) to 192.168.27.98:5060 --->
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.27.98:5060;branch=z9hG4bK-16ba5-58c7d35-
4a11b393;received=192.168.27.98;rport=5060
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>;tag=as3903248a
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 1 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE,
NOTIFY
Supported: replaces
Proxy-Authenticate: Digest algorithm=MD5, realm="ostergaard.net",
nonce="19ae9086"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '10b2f2f0-621ba8c0-13c4-40030-
16ba5-2f6d4897-16ba5' in 32000 ms (Method: INVITE)
Found user '018'
Ildvaeg*CLI>
<--- SIP read from 192.168.27.98:5060 --->
ACK sip:**1 at 192.168.2.1 SIP/2.0
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>;tag=as3903248a
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 1 ACK
Via: SIP/2.0/UDP 192.168.27.98:5060;rport;branch=z9hG4bK-16ba5-
58c7d35-4a11b393
Max-Forwards: 70
Contact: <sip:018 at 192.168.27.98:5060>
Content-Length: 0
<------------->
--- (9 headers 0 lines) ---
Ildvaeg*CLI>
<--- SIP read from 192.168.27.98:5060 --->
INVITE sip:**1 at 192.168.2.1 SIP/2.0
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 2 INVITE
Via: SIP/2.0/UDP 192.168.27.98:5060;rport;branch=z9hG4bK-16ba5-
58c7d53-6bede6e9
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER,
SUBSCRIBE, NOTIFY, MESSAGE, INFO
User-Agent: ATMEL_UA v0.0.25-alpha
Max-Forwards: 70
Contact: <sip:018 at 192.168.27.98:5060>
Proxy-Authorization: Digest
username="018",realm="ostergaard.net",nonce="19ae9086",uri="sip:**1 at 1
92.168.2.1",response="512fdfcf3ad644a79d92e4037679eee9",algorithm=M
D5
Content-Type: application/sdp
Content-Length: 334
v=0
o=018 12119074 77112119074177 IN IP4 192.168.27.98
s=audio
c=IN IP4 192.168.27.98
t=0 0
m=audio 16426 RTP/AVP 0 8 18 4 97 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16
a=ptime:30
<------------->
--- (13 headers 15 lines) ---
Sending to 192.168.27.98 : 5060 (NAT)
Using INVITE request as basis request - 10b2f2f0-621ba8c0-13c4-40030-
16ba5-2f6d4897-16ba5
Found user '018'
Found RTP audio format 0
Found RTP audio format 8
Found RTP audio format 18
Found RTP audio format 4
Found RTP audio format 97
Found RTP audio format 101
Peer audio RTP is at port 192.168.27.98:16426
Found description format PCMU for ID 0
Found description format PCMA for ID 8
Found description format G729 for ID 18
Found description format G723 for ID 4
Found description format iLBC for ID 97
Found description format telephone-event for ID 101
Capabilities: us - 0x4 (ulaw), peer - audio=0x50d
(g723|ulaw|alaw|g729|ilbc)/video=0x0 (nothing), combined - 0x4 (ulaw)
Non-codec capabilities (dtmf): us - 0x0 (nothing), peer - 0x1 (telephone-
event), combined - 0x0 (nothing)
Peer audio RTP is at port 192.168.27.98:16426
Looking for **1 in from-internal (domain 192.168.2.1)
<--- Reliably Transmitting (no NAT) to 192.168.27.98:5060 --->
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 192.168.27.98:5060;branch=z9hG4bK-16ba5-58c7d53-
6bede6e9;received=192.168.27.98;rport=5060
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>;tag=as3903248a
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 2 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE,
NOTIFY
Supported: replaces
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '10b2f2f0-621ba8c0-13c4-40030-
16ba5-2f6d4897-16ba5' in 32000 ms (Method: INVITE)
Ildvaeg*CLI>
<--- SIP read from 192.168.27.98:5060 --->
ACK sip:**1 at 192.168.2.1 SIP/2.0
From: <sip:018 at 192.168.2.1:5060>;tag=10c4a070-621ba8c0-13c4-40030-
16ba5-550488a5-16ba5
To: <sip:**1 at 192.168.2.1>;tag=as3903248a
Call-ID: 10b2f2f0-621ba8c0-13c4-40030-16ba5-2f6d4897-16ba5
CSeq: 2 ACK
Via: SIP/2.0/UDP 192.168.27.98:5060;rport;branch=z9hG4bK-16ba5-
58c7d53-6bede6e9
Max-Forwards: 70
Contact: <sip:018 at 192.168.27.98:5060>
Content-Length: 0
<------------->
--- (9 headers 0 lines) ---
Quote: | Check your features.conf file and make sure that combination or a
similar combination (*1 or ** ) for instance isn't defined in there for
some reason.
Matt Watson wrote:
Quote: | Might want to do a "sip set debug peer <peer id>"
You should then be able to see the sip packet dumps that are going
|
| between the phone and *. Might give you some clues.
-----------------------------------------------------------
Henrik ?stergaard Madsen Phone: +45 44 48 44 92
PhD, M.Sc. Cell: +45 30 94 02 88
Mosegard Park 42 email: Henrik at Ostergaard.net
DK-3500 V?rl?se WWW homepage:
Denmark http://www.Ostergaard.net/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
--
Best Regards
Rizwan Hisham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080529/01deed18/attachment.htm |
|
Back to top |
|
|
Henrik at Ostergaard.net Guest
|
Posted: Thu May 29, 2008 6:59 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
No it is unfortunately not that. Calling '**11' in stead DOES come
out with an 'extension not found'. But '**1' does not come with ANY
output except for the sip logging. And I DO have '**1' defined in
the extensions. '**' does not produce any output either, and this is
not defiend in extensions. The sip package dump in the former post
was the entire output from Asterisk.. |
|
Back to top |
|
|
stevej456 at gmail.com Guest
|
Posted: Thu May 29, 2008 10:37 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
This suggests to me that you might have to make a change to the
phone's internal dialplan string. What is it now in the SPA941 (at
the bottom of the EXT1 tab on the phone's web configuration screen)?
S.
On Wed, May 28, 2008 at 10:53 AM, Henrik Ostergaard Madsen
<Henrik at ostergaard.net> wrote:
Quote: | I am experiencing problems calling '**1' through astrisk from an VOIP
telephone. Asterisk appearently does not accept the call and never show
any indication of an incoming call (using asterisk -rvvvvvvvvvvvvvvvvvv).
On the phone, I get an immideate 'Call ended'. This occurs on both an
Linksysy SPA941 and an LIP TA100. The same happens with '**'
Using '**11' or '*1' or '*11' instead, the call gets right through..
I can see on tcpdump that the SIP packages does reach the asterisk server
and gets answered.
Does anyone have a clue on what is going on?
Regards
Henrik
-----------------------------------------------------------
Henrik ?stergaard Madsen Phone: +45 44 48 44 92
PhD, M.Sc. Cell: +45 30 94 02 88
Mosegard Park 42 email: Henrik at Ostergaard.net
DK-3500 V?rl?se WWW homepage:
Denmark http://www.Ostergaard.net/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
|
|
Back to top |
|
|
joakimsen at gmail.com Guest
|
Posted: Thu May 29, 2008 11:51 pm Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Asterisk 1.4.20.1
Polycom 501 v 3.0.1.0032
[May 30 00:12:54] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**1'
rejected because extension not found.
[May 30 00:14:25] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**' rejected
because extension not found.
I did not even modify the dial plan on the phone, just press **1 and
dial. Make sure the configuration (dialplan) on the Linksys is
correct, see http://spc.pifiu.com for details.
On Thu, May 29, 2008 at 7:59 AM, Henrik ?stergaard Madsen
<Henrik at ostergaard.net> wrote:
Quote: | No it is unfortunately not that. Calling '**11' in stead DOES come
out with an 'extension not found'. But '**1' does not come with ANY
output except for the sip logging. And I DO have '**1' defined in
the extensions. '**' does not produce any output either, and this is
not defiend in extensions. The sip package dump in the former post
was the entire output from Asterisk..
From my point of view it is beginning to look like a bug in Asterisk
rather than a configuration issue
Regards
Henrik
Quote: | seems like asterisk could not find the extension number "**1". does
your
context "from-internal" have this extensions? if not then create one
or
include the context which contains the extension **1 in
from-internal and
then try.
|
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
|
|
Back to top |
|
|
Henrik at Ostergaard.net Guest
|
Posted: Fri May 30, 2008 12:12 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Quote: | Asterisk 1.4.20.1
Polycom 501 v 3.0.1.0032
[May 30 00:12:54] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**1'
rejected because extension not found.
[May 30 00:14:25] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**'
rejected
because extension not found.
I did not even modify the dial plan on the phone, just press **1 and
dial. Make sure the configuration (dialplan) on the Linksys is
correct, see http://spc.pifiu.com for details.
|
Interresting - I AM sure the dial plan does forward the call on the
Linksys. The TA100 doesnt even have a dialplan - everything is
forwarded raw - and it is the same issue there.
But the bottom line of this must be that my Asterisk is somehow not
correct. Either the configuration or the Asterisk itself. I cannot
see why a configuration error should come with such a behavior
(without showing something in the debug output). But updating to the
latest Asterisk should not be a big thing.
Thanks for the help, I will try that over the weekend.
/Henrik |
|
Back to top |
|
|
blue at cmd.nu Guest
|
Posted: Sat May 31, 2008 6:01 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Hello.
On my Linksys SPA961 I had to change the dialplan string in order for **X to
work.
Greetings,
On Fri, May 30, 2008 at 7:12 AM, Henrik ?stergaard Madsen <
Henrik at ostergaard.net> wrote:
Quote: |
Quote: | Asterisk 1.4.20.1
Polycom 501 v 3.0.1.0032
[May 30 00:12:54] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**1'
rejected because extension not found.
[May 30 00:14:25] NOTICE[26924]: chan_sip.c:14033
handle_request_invite: Call from 'SIP_PEER' to extension '**'
rejected
because extension not found.
I did not even modify the dial plan on the phone, just press **1 and
dial. Make sure the configuration (dialplan) on the Linksys is
correct, see http://spc.pifiu.com for details.
|
Interresting - I AM sure the dial plan does forward the call on the
Linksys. The TA100 doesnt even have a dialplan - everything is
forwarded raw - and it is the same issue there.
But the bottom line of this must be that my Asterisk is somehow not
correct. Either the configuration or the Asterisk itself. I cannot
see why a configuration error should come with such a behavior
(without showing something in the debug output). But updating to the
latest Asterisk should not be a big thing.
Thanks for the help, I will try that over the weekend.
/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
--
Christian Svensson
Command Systems
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080531/f3131715/attachment.htm |
|
Back to top |
|
|
Henrik at ostergaard.net Guest
|
Posted: Sun Jun 01, 2008 5:03 pm Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
I have now upgraded to the latest Asterisk 1.4.20.1 and add-ons 1.4.6 without any luck - so I
started dismantling my dialplan.
It seems that the incoming catch:
exten => _**[1234567890].,1,NoOp(Incoming call to a quickdial number ${EXTEN})
does NOT work with **1 - in stead of printing some debug, it just closes the channel without
any warning, error or the like.. But it does work with **11!
Changing it to
exten => _**[1234567890],1,NoOp(Incoming call to a quickdial number ${EXTEN})
makes it work (with **1 etc - not **11)
- so I have made it do what I want, even as I still think it is a bug..
/Henrik |
|
Back to top |
|
|
rob at hillis.dyndns.org Guest
|
Posted: Sun Jun 01, 2008 6:50 pm Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Not a bug at all. "." as a pattern match means "1 or more digits" - so
your pattern match means ** followed by a digit between 0 and 9,
followed by one or more digits. Removing the "." means that you then
match **, followed by a digit between 0 and 9.
If you want to match ** followed by a digit between 1 and 9, followed by
zero or more digits, the use the extension pattern "_**X!". X matches
any digit from 0-9, so your pattern match is unnecessary. ! matches
zero or more digits.
Henrik Ostergaard Madsen wrote:
Quote: | I have now upgraded to the latest Asterisk 1.4.20.1 and add-ons 1.4.6 without any luck - so I
started dismantling my dialplan.
It seems that the incoming catch:
exten => _**[1234567890].,1,NoOp(Incoming call to a quickdial number ${EXTEN})
does NOT work with **1 - in stead of printing some debug, it just closes the channel without
any warning, error or the like.. But it does work with **11!
Changing it to
exten => _**[1234567890],1,NoOp(Incoming call to a quickdial number ${EXTEN})
makes it work (with **1 etc - not **11)
- so I have made it do what I want, even as I still think it is a bug..
/Henrik
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
!DSPAM:4843121e67795358292934!
|
|
|
Back to top |
|
|
Henrik at Ostergaard.net Guest
|
Posted: Mon Jun 02, 2008 12:24 am Post subject: [asterisk-users] Calling '**1' through Asterisk |
|
|
Argh - you are perfectly right. I have been too far away from the
dialplan for too long
Thanks for the help!
/Henrik
Quote: | Not a bug at all. "." as a pattern match means "1 or more digits" -
so
your pattern match means ** followed by a digit between 0 and 9,
followed by one or more digits. Removing the "." means that you
then
match **, followed by a digit between 0 and 9.
If you want to match ** followed by a digit between 1 and 9,
followed by
zero or more digits, the use the extension pattern "_**X!". X
matches
any digit from 0-9, so your pattern match is unnecessary. ! matches
zero or more digits.
Henrik Ostergaard Madsen wrote:
Quote: | I have now upgraded to the latest Asterisk 1.4.20.1 and add-ons
1.4.6 without any luck - so I
started dismantling my dialplan.
It seems that the incoming catch:
exten => _**[1234567890].,1,NoOp(Incoming call to a quickdial
number ${EXTEN})
does NOT work with **1 - in stead of printing some debug, it just
closes the channel without
any warning, error or the like.. But it does work with **11!
Changing it to
exten => _**[1234567890],1,NoOp(Incoming call to a quickdial
number ${EXTEN})
makes it work (with **1 etc - not **11)
- so I have made it do what I want, even as I still think it is a
bug..
|
|
|
|
Back to top |
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|