[Freeswitch-dev] Call relaying (ISDN <> Freeswitch <> ISDN)

Moises Silva moises.silva at gmail.com
Sun Sep 8 10:20:25 MSD 2013

On Sat, Sep 7, 2013 at 4:08 PM, Markus Müller <freeswitchdev at priv.de> wrote:

>  Hi all,
> hi Markus,
> how do you determine if it's a complete number? Do you expect the outgoing
> ISDN channel to tell you that?
> Sorry that I don't have all details; I am not as familary as I want to
> with the ISDN protocols. But I know that each number goes one by one to the
> outgoing ISDN and then outgoint ISDN tells you back when you have reached a
> destination. If needed I can make a log when I have my Siemens Hipath
> placed behind my Freeswitch in NT mode; there you can see the numbers
> comming one by one.
> I also wonder what happens if you attach an ISDN-SIP gateway, like Patton.
> Will you have a new SIP message (which?) on every dialed digit?
> Normaly all the products do the "overlap dialing" crap, as mentioned in my
> first email. I don't know for sure but I think there is no alternative,
> especially if you make only SIP and not ISDN.
> No comments about my design suggestion?
Your design suggestion is pretty thin on details, so is hard to comment on

However, overall it does not sound like a good idea to me to try to bridge
a call without going through the FreeSWITCH core.

I believe your best shot at getting this done and integrated would be to
make it work with the existing bridge() application. This is a rough
description of how to do it:

1. Send the call up from the signaling stack to FreeSWITCH immediately so
the call is sent to the routing engine and you can call the bridge()
application on an outbound FreeTDM channel.

2. The outbound channel sends the first call message (ie SETUP)

3. Relay the following digits as subsequent signaling messages from the
inbound leg to the outbound leg. On the FreeTDM side using
FTDM_SIGEVENT_COLLECTED_DIGIT, then enqueuing a freeswitch message such as
SWITCH_MESSAGE_INDICATE_INFO, on the outgoing leg you would receive the
indication and send the digits to the upstream provider.

Note you described some sort of pass-thru overlap functionality, if we
wanted to implement overlap dialing where FreeSWITCH takes the routing
decision based on digits as received some extra effort is required to have
XML re-evaluated for each digit received.



*Moises Silva
**Manager, Software Engineering***

msilva at sangoma.com

Sangoma Technologies

100 Renfrew Drive, Suite 100, Markham, ON L3R 9R6 Canada

t.   +1 800 388 2475 (N. America)

t.   +1 905 474 1990 x128

f.   +1 905 474 9223


 | Solutions<http://sangoma.com/solutions?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Events<http://sangoma.com/about_us/events?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Contact<http://www.sangoma.com/contact?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Wiki<http://wiki.sangoma.com/?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Facebook<http://www.facebook.com/pages/Sangoma-VoIP-Cards/43578453335?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Twitter<http://www.twitter.com/sangoma?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>`|
| YouTube<http://www.youtube.com/sangomatechnologies?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20130908/5b458cf1/attachment.html 

Join us at ClueCon 2013 Aug 6-8, 2013
More information about the FreeSWITCH-dev mailing list