[Freeswitch-users] freetdm and destination_number

Tim Bock jtbock at synacktics.com
Fri Aug 24 07:36:46 MSD 2012


Hello,

I'm rather new with FreeSWITCH, migrating over from an asterisk setup.

I have a Digium TDM card, with 3 fxo ports and 1 fxs port.  I have 
everything mostly working, but I'm having an issue with incoming fxo 
calls.  I've found examples where people have used destination_number in 
their condition, but this doesn't seem to work for me.  I can 
successfully use
> <condition field="${channel_name}" expression="^(FreeTDM/2:3/)">

but not

> <condition field="destination_number" expression="(7832889)$"/>
The issue seems to be that destination_number is set to 2 early on, somehow:
> 012-08-23 20:40:43.213780 [DEBUG] ftmod_analog.c:646 [s2c3][1:3] 
> Executing stat
> e handler on 2:3 for RING
> 2012-08-23 20:40:43.213780 [DEBUG] mod_freetdm.c:1992 got FXO sig 2:3 
> [START]
> 2012-08-23 20:40:43.213780 [DEBUG] ftdm_io.c:3131 [s2c3][1:3] Enabled 
> software D
> TMF detector
> 2012-08-23 20:40:43.213780 [DEBUG] mod_freetdm.c:407 Set codec PCMU 20ms
> 2012-08-23 20:40:43.213780 [DEBUG] mod_freetdm.c:1740 Connect inbound 
> channel Fr
> eeTDM/2:3/2
so that later:
> Dialplan: FreeTDM/2:3/2 Regex (FAIL) [fxo_incoming] 
> destination_number(2) =~ /(78328
> 89)$/ break=on-false
Any ideas on what I am doing wrong?  I can make it work using the 
channel_name variable, but using destination_number would be much more 
convenient.

Thank you,
Tim



Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list