The <something> is a number saved in the variable modem_digits on the channel to do whatever you want with in the cdr etc....Its not passed to the the modem device.

This is an obvious case for a JIRA.... I need to come up with a way to explain the order of magnitude difference there is trying to help someone over the mailing list vs JIRA when you have to start providing patches etc.

If your would take this patch and run it to get more details and open a JIRA and post the results I would appreciate it.
 




On Tue, Dec 11, 2012 at 2:16 PM, Alex Crow <acrow@integrafin.co.uk> wrote:
On 11/12/12 20:00, Anthony Minessale wrote:
> Looking again, I'm not sure what the modem/10/a is supposed to be
>
> There is a such thing as modem/a/<number> but
>
> if you are looking to bridge to slot 23 try
>
> modem/23/${destination_number}
>
> if you are getting a different slot maybe you simlinks are messed up,
> you need to make sure they are recreated whenever you restart so maybe
> that patch you are using has an issue.
>
>
>

Hi,

I will try to get full logs to you when I can, possibly tomorrow as I
have a stinking cold today. However I can tell you my symlinks are fine
- and 90% of the time the inbound fax gets to the right modem. Just that
every so often FS seems to send it to the wrong one.

On calls that are coming *in* to a modem device, I don't see how there
even can be a destination number. It's just a modem surely - the
destination is simply a device on which Hylafax is listening. I can
completely understand how when you call out through the virtual modem
you need to supply a number, but on inbound it doesn't make any sense to
me, we're not routing into a SIP endpoint but a virtual device.

Looking at the source code told me to use modem/slot/<something>, but
for inbound calls I don't know what <something> should be.

If I have got something topsy-turvy please enlighten me, I'm quite happy
to be corrected!

Cheers

Alex

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900