Re: [asterisk-users] J1/INS1500 and the Redirect Number
and what if you do:
zap debug span 2
OR:
zap intense debug span 2
Is the value anywhere there?
On 1/19/07, Gary Mensenares [EMAIL PROTECTED] wrote:
Hello Andrew!
Thanks for taking the time to reply.
Sorry but no, it doesnt seem to show up.
Here's my dial plan:
exten = _X.,s,Answer()
exten = _X.,n,Set(Ani=${CALLERID(ani)})
exten = _X.,n,Set(Dnis=${CALLERID(dnis)})
exten = _X.,n,Set(Rdnis=${CALLERID(rdnis)})
exten = _X.,n,NoOp(ANI: ${Ani})
exten = _X.,n,NoOp(DNIS: ${dnis})
exten = _X.,n,NoOp(RDNIS: ${rdnis})
exten = _X.,n,SayDigits(${Ani})
exten = _X., Hangup()
This is what I get:
[Jan 19 14:20:14] DEBUG[24089]: chan_zap.c:7649 pri_find_empty_chan: Found
empty available channel 0/23
-- Accepting call from '090' to '4590' on channel 0/23, span 2
[Jan 19 14:20:14] DEBUG[24089]: chan_zap.c:1458 zt_enable_ec: Enabled echo
cancellation on channel 47
-- Executing [EMAIL PROTECTED]:1] Answer(Zap/47-1, ) in new stack
[Jan 19 14:20:14] DEBUG[24083]: channel.c:895 channel_find_locked: Avoiding
initial deadlock for channel '0x8b86720'
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is '090'
-- Executing [EMAIL PROTECTED]:2] Set(Zap/47-1, Ani=090) in new
stack
[Jan 19 14:20:14] ERROR[7387]: func_callerid.c:91 callerid_read: Unknown
callerid data type 'dnis'.
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is ''
-- Executing [EMAIL PROTECTED]:3] Set(Zap/47-1, Dnis=) in new stack
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is ''
-- Executing [EMAIL PROTECTED]:4] Set(Zap/47-1, Rdnis=) in new stack
-- Executing [EMAIL PROTECTED]:5] NoOp(Zap/47-1, ANI: 090)
in new stack
-- Executing [EMAIL PROTECTED]:6] NoOp(Zap/47-1, DNIS: ) in new stack
-- Executing [EMAIL PROTECTED]:7] NoOp(Zap/47-1, RDNIS: ) in new
stack
-- Executing [EMAIL PROTECTED]:8] SayDigits(Zap/47-1, 090) in
new stack
However, we are quite positive that the redirect number is in there because on
mobile terminals, both the redirect and the ani are identified.
Anyone out there had any luck with the RDNIS before?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Joakimsen
Sent: Friday, January 19, 2007 9:20 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] J1/INS1500 and the Redirect Number
Is it not coming in as CallerID(RDIS)? The specifications for
the service don't seem too different from any other PRI.
On 1/16/07, Gary Mensenares [EMAIL PROTECTED] wrote:
Hi everyone!
I'm wondering if anyone on the list had the opportunity to
work with
an NTT INS1500 ISDN PRI service before.
You see, in Japan, if you receive a call that was just forwarded by
another number, the call presentation not only includes the caller
(ANI) and your number (DNIS), it will also usually include the
forwarding number (REDIRECT). Does anybody know how to
extract this field on Asterisk?
For reference, you can look at
http://www.ntt-east.co.jp/ISDN/tech/spec/espec/3-5/content_3.html.
This is the full specification of INS 1500 signalling. Any
assistance
would be very much appreciated.
Thanks again!
Sincerely,
Jug Mensenares
___
--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
___
--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] J1/INS1500 and the Redirect Number
Is it not coming in as CallerID(RDIS)? The specifications for the service don't seem too different from any other PRI. On 1/16/07, Gary Mensenares [EMAIL PROTECTED] wrote: Hi everyone! I'm wondering if anyone on the list had the opportunity to work with an NTT INS1500 ISDN PRI service before. You see, in Japan, if you receive a call that was just forwarded by another number, the call presentation not only includes the caller (ANI) and your number (DNIS), it will also usually include the forwarding number (REDIRECT). Does anybody know how to extract this field on Asterisk? For reference, you can look at http://www.ntt-east.co.jp/ISDN/tech/spec/espec/3-5/content_3.html. This is the full specification of INS 1500 signalling. Any assistance would be very much appreciated. Thanks again! Sincerely, Jug Mensenares ___ --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] J1/INS1500 and the Redirect Number
Hello Andrew!
Thanks for taking the time to reply.
Sorry but no, it doesnt seem to show up.
Here's my dial plan:
exten = _X.,s,Answer()
exten = _X.,n,Set(Ani=${CALLERID(ani)})
exten = _X.,n,Set(Dnis=${CALLERID(dnis)})
exten = _X.,n,Set(Rdnis=${CALLERID(rdnis)})
exten = _X.,n,NoOp(ANI: ${Ani})
exten = _X.,n,NoOp(DNIS: ${dnis})
exten = _X.,n,NoOp(RDNIS: ${rdnis})
exten = _X.,n,SayDigits(${Ani})
exten = _X., Hangup()
This is what I get:
[Jan 19 14:20:14] DEBUG[24089]: chan_zap.c:7649 pri_find_empty_chan: Found
empty available channel 0/23
-- Accepting call from '090' to '4590' on channel 0/23, span 2
[Jan 19 14:20:14] DEBUG[24089]: chan_zap.c:1458 zt_enable_ec: Enabled echo
cancellation on channel 47
-- Executing [EMAIL PROTECTED]:1] Answer(Zap/47-1, ) in new stack
[Jan 19 14:20:14] DEBUG[24083]: channel.c:895 channel_find_locked: Avoiding
initial deadlock for channel '0x8b86720'
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is '090'
-- Executing [EMAIL PROTECTED]:2] Set(Zap/47-1, Ani=090) in new
stack
[Jan 19 14:20:14] ERROR[7387]: func_callerid.c:91 callerid_read: Unknown
callerid data type 'dnis'.
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is ''
-- Executing [EMAIL PROTECTED]:3] Set(Zap/47-1, Dnis=) in new stack
[Jan 19 14:20:14] DEBUG[7387]: pbx.c:1621 pbx_substitute_variables_helper_full:
Function result is ''
-- Executing [EMAIL PROTECTED]:4] Set(Zap/47-1, Rdnis=) in new stack
-- Executing [EMAIL PROTECTED]:5] NoOp(Zap/47-1, ANI: 090)
in new stack
-- Executing [EMAIL PROTECTED]:6] NoOp(Zap/47-1, DNIS: ) in new stack
-- Executing [EMAIL PROTECTED]:7] NoOp(Zap/47-1, RDNIS: ) in new
stack
-- Executing [EMAIL PROTECTED]:8] SayDigits(Zap/47-1, 090) in
new stack
However, we are quite positive that the redirect number is in there because on
mobile terminals, both the redirect and the ani are identified.
Anyone out there had any luck with the RDNIS before?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Joakimsen
Sent: Friday, January 19, 2007 9:20 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] J1/INS1500 and the Redirect Number
Is it not coming in as CallerID(RDIS)? The specifications for
the service don't seem too different from any other PRI.
On 1/16/07, Gary Mensenares [EMAIL PROTECTED] wrote:
Hi everyone!
I'm wondering if anyone on the list had the opportunity to
work with
an NTT INS1500 ISDN PRI service before.
You see, in Japan, if you receive a call that was just forwarded by
another number, the call presentation not only includes the caller
(ANI) and your number (DNIS), it will also usually include the
forwarding number (REDIRECT). Does anybody know how to
extract this field on Asterisk?
For reference, you can look at
http://www.ntt-east.co.jp/ISDN/tech/spec/espec/3-5/content_3.html.
This is the full specification of INS 1500 signalling. Any
assistance
would be very much appreciated.
Thanks again!
Sincerely,
Jug Mensenares
___
--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
___
--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
[asterisk-users] J1/INS1500 and the Redirect Number
Hi everyone! I'm wondering if anyone on the list had the opportunity to work with an NTT INS1500 ISDN PRI service before. You see, in Japan, if you receive a call that was just forwarded by another number, the call presentation not only includes the caller (ANI) and your number (DNIS), it will also usually include the forwarding number (REDIRECT). Does anybody know how to extract this field on Asterisk? For reference, you can look at http://www.ntt-east.co.jp/ISDN/tech/spec/espec/3-5/content_3.html. This is the full specification of INS 1500 signalling. Any assistance would be very much appreciated. Thanks again! Sincerely, Jug Mensenares ___ --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
