Hello,
I have a carrier providing a T1 E&M-II wink start trunk to a Fujitsu
F9600.  They provide caller-id information by formatting the digits send
as *ANI*DNIS.  If I configure the controller as:
ds0-group 1 timeslots 1-24 type e&m-wink-start dnis

I can place outbound calls, but for inbound calls I'll see a number like
*3375551212*3600* , and this of course would not match anything my
dail-peers or CallManager expects.  Can a TCL script be used to break
this number up and pass the caller-id and DID to CallManager?  The IOS
is 12.4T AdvancedIP Services, and CCM 4.1.3sr2

Thanks,

-Patrick

[ Post a follow-up to this message ]

htis is Feature group D signaling.  did youtr fgd ds0 group?

also, did you try eana for inbound and outbound?
http://www.cisco.com/en/US/partner/tech/tk652/tk653/
technologies_tech_note09186a00800e2560.shtml

otherwise:
http://www.cisco.com/en/US/partner/...osswrel/ps1834/
products_feature_guide09186a008007fe27.html

/Wes

On Dec 28, 2005, at 12:18 PM, Patrick Mowry wrote:

Hello,
I have a carrier providing a T1 E&M-II wink start trunk to a Fujitsu
F9600.  They provide caller-id information by formatting the digits send
as *ANI*DNIS.  If I configure the controller as:
ds0-group 1 timeslots 1-24 type e&m-wink-start dnis

I can place outbound calls, but for inbound calls I'll see a number like
*3375551212*3600* , and this of course would not match anything my
dail-peers or CallManager expects.  Can a TCL script be used to break
this number up and pass the caller-id and DID to CallManager?  The IOS
is 12.4T AdvancedIP Services, and CCM 4.1.3sr2

Thanks,

-Patrick

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]

Yes, it is possible.

you should use the "set ani" and "set dnis" commands. In example, configure
in the incoming TCL to set both the ANI and DNIS
to the "ANI" number. Then configure an outgoing sed-style translation to the
CCM to strip the "*" and the second part from the ANI
and to the "*" and first part from the DNIS. Should work, in theory <grin>

----- Original Message -----
From: "Patrick Mowry" <pmowry@getgds.com>
To: <cisco-voip@puck.nether.net>
Sent: Wednesday, December 28, 2005 7:18 PM
Subject: [cisco-voip] TCL script to parse *ANI*DNIS*


> Hello,
>  I have a carrier providing a T1 E&M-II wink start trunk to a Fujitsu
> F9600.  They provide caller-id information by formatting the digits send
> as *ANI*DNIS.  If I configure the controller as:
> ds0-group 1 timeslots 1-24 type e&m-wink-start dnis
>
> I can place outbound calls, but for inbound calls I'll see a number like
> *3375551212*3600* , and this of course would not match anything my
> dail-peers or CallManager expects.  Can a TCL script be used to break
> this number up and pass the caller-id and DID to CallManager?  The IOS
> is 12.4T AdvancedIP Services, and CCM 4.1.3sr2
>
> Thanks,
>
> -Patrick
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

-----Original Message-----
From: Teodor Georgiev [mailto:tgeorgiev@is-bg.net]
Sent: Monday, January 02, 2006 5:14 AM
To: Patrick Mowry; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] TCL script to parse *ANI*DNIS*


Yes, it is possible.

you should use the "set ani" and "set dnis" commands. In example,
configure
in the incoming TCL to set both the ANI and DNIS
to the "ANI" number. Then configure an outgoing sed-style translation to
the
CCM to strip the "*" and the second part from the ANI
and to the "*" and first part from the DNIS. Should work, in theory
<grin>

---------------------------

How does this look?  Now I need to find out if a 2800 supports custom
scripts.  I'm having trouble getting it loaded. AS for Feature Group D,
This trunk is using DTMF signaling, and it is not sending in
#<DD><ANI>*#<DNIS>* format like cisco expects.  My understanding is I
can only change this expected format on the as5X00 gateways.

Thanks for all the help,

-Patrick



# app_NetPro.tcl
# Script Version 0.0.1
#------------------------------------------------------------------
#
# This tcl script collects DTMF digits, separates into ANI and DNIS
# Then places the call.
#
#
proc init { } {
global param
set param(interruptPrompt) true
}
#################

proc act_Setup { } {
global dest
leg setupack leg_incoming
leg collectdigits leg_incoming param
}
}
################

proc act_GotDest { } {
global ani
global dnis
global fields
global digits
set status [infotag get evt_status]
if { $status == "cd_004" } {
set digits [infotag get evt_dcdigits]
set fields [split $digits *]
set ani [lindex $fields 1]
set dnis [lindex $fileds 2]
leg proceeding leg_incoming

set callinfo(destinationNum) $dnis
set callinfo(originationNum) $ani

leg setup $dnis callInfo leg_incoming
} else {
puts "\nCall [infotag get con_all] got event $status collecting
destination"
call close
}
}
################

proc act_Ignore { } {
# Dummy
puts "Event Capture"
}
################

proc act_Cleanup { } {
call close
}
#----------------------------------
# State Machine
#----------------------------------
set TopFSM(any_state,ev_disconnected) "act_Cleanup,same_state"
set TopFSM(CALL_INIT,ev_setup_indication) "act_Setup,GETDEST"
set TopFSM(GETDEST,ev_collectdigits_done) "act_GotDest,PLACECALL"
set TopFSM(PLACECALL,ev_setup_done) "act_CallSetupDone,CALLACTIVE"
set TopFSM(CALLACTIVE,ev_disconnected) "act_Cleanup,CALLDISCONNECTED"
set  TopFSM(CALLDISCONNECTED,ev_disconnected)
 "act_Cleanup,same_state"
set TopFSM(CALLDISCONNECTED,ev_media_done) "act_Cleanup,same_state"
set  TopFSM(CALLDISCONNECTED,ev_disconnect_do
ne) "act_Cleanup,same_state"
set TopFSM(CALLDISCONNECTED,ev_leg_timer) "act_Cleanup,same_state"

[ Post a follow-up to this message ]

Start with this command:

show call application voice summary

and see at the bottom the TCL version your IOS supports.

----- Original Message -----
From: "Patrick Mowry" <pmowry@getgds.com>
To: "Teodor Georgiev" <tgeorgiev@is-bg.net>; <cisco-voip@puck.nether.net>
Sent: Tuesday, January 24, 2006 11:18 PM
Subject: RE: [cisco-voip] TCL script to parse *ANI*DNIS*



-----Original Message-----
From: Teodor Georgiev [mailto:tgeorgiev@is-bg.net]
Sent: Monday, January 02, 2006 5:14 AM
To: Patrick Mowry; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] TCL script to parse *ANI*DNIS*


Yes, it is possible.

you should use the "set ani" and "set dnis" commands. In example,
configure
in the incoming TCL to set both the ANI and DNIS
to the "ANI" number. Then configure an outgoing sed-style translation to
the
CCM to strip the "*" and the second part from the ANI
and to the "*" and first part from the DNIS. Should work, in theory
<grin>

---------------------------

How does this look?  Now I need to find out if a 2800 supports custom
scripts.  I'm having trouble getting it loaded. AS for Feature Group D,
This trunk is using DTMF signaling, and it is not sending in
#<DD><ANI>*#<DNIS>* format like cisco expects.  My understanding is I
can only change this expected format on the as5X00 gateways.

Thanks for all the help,

-Patrick



# app_NetPro.tcl
# Script Version 0.0.1
#------------------------------------------------------------------
#
# This tcl script collects DTMF digits, separates into ANI and DNIS
# Then places the call.
#
#
proc init { } {
global param
set param(interruptPrompt) true
}
#################

proc act_Setup { } {
global dest
leg setupack leg_incoming
leg collectdigits leg_incoming param
}
}
################

proc act_GotDest { } {
global ani
global dnis
global fields
global digits
set status [infotag get evt_status]
if { $status == "cd_004" } {
set digits [infotag get evt_dcdigits]
set fields [split $digits *]
set ani [lindex $fields 1]
set dnis [lindex $fileds 2]
leg proceeding leg_incoming

set callinfo(destinationNum) $dnis
set callinfo(originationNum) $ani

leg setup $dnis callInfo leg_incoming
} else {
puts "\nCall [infotag get con_all] got event $status collecting
destination"
call close
}
}
################

proc act_Ignore { } {
# Dummy
puts "Event Capture"
}
################

proc act_Cleanup { } {
call close
}
#----------------------------------
# State Machine
#----------------------------------
set TopFSM(any_state,ev_disconnected) "act_Cleanup,same_state"
set TopFSM(CALL_INIT,ev_setup_indication) "act_Setup,GETDEST"
set TopFSM(GETDEST,ev_collectdigits_done) "act_GotDest,PLACECALL"
set TopFSM(PLACECALL,ev_setup_done) "act_CallSetupDone,CALLACTIVE"
set TopFSM(CALLACTIVE,ev_disconnected) "act_Cleanup,CALLDISCONNECTED"
set  TopFSM(CALLDISCONNECTED,ev_disconnected)
 "act_Cleanup,same_state"
set TopFSM(CALLDISCONNECTED,ev_media_done) "act_Cleanup,same_state"
set  TopFSM(CALLDISCONNECTED,ev_disconnect_do
ne) "act_Cleanup,same_state"
set TopFSM(CALLDISCONNECTED,ev_leg_timer) "act_Cleanup,same_state"

[ Post a follow-up to this message ]