On 8 June 2011 18:44, David Ponzone <david.ponzone@ipeva.fr> wrote:

Christian, well you should first tell us what kinda of ISDN you ordered from your local telco. And also, check if the card/drivers are configured with the right ISDN type. That could explain why you don't get the DID. I suppose there are other possible reasons: How many DID do you have ? If only one, I suppose some telcos may send you the call without anything, as you dont need the info anyway. That would be ugly, but some telcos do ugly things in some places.

Well the line is in our lab since ages, so i can't really tell you what "exactly" has been ordered back then :-) It's an EuroISDN-BRI without a MSN but an unbounded number of DIDs(Fixed 7-digit Headnumber plus up to 5 digit extensions - which is basically a standard BRI-line in Austria). As the outbound calls work fine(headnumber+extensions are delivered) i assume it's not exactly an configuration issue. According to my colleagues the DID has always been sent(With proprietary PBX). A few harder facts - my configuration: http://pastebin.com/Kc4BPL9E This in old paste of a previous problem, but the configuration is still the same. If i can provide you with more precise information, please let me know what you need, a ISDN-trace is in the paste in my previous mail. I'll run a test on a different box with a Sangoma card tomorrow, i just hoped someone could give me a jump-start with the information i posted earlier. Best, Christian

On 8 June 2011 20:43, Stefan Knoblich <stkn@freeswitch.org> wrote:

Am Wednesday 08 June 2011 schrieb Christian Benke:

...

My FS is connected to a plain BRI-line via a HFC-S PCI-card. On inbound calls i don't receive a dialed number. Please see the debug at http://pastebin.freeswitch.org/16456 for details. Do i have to fetch the DID from a variable before i can handle the call or is there some other problem, which i assume?

That SETUP message at the top isn't valid, AFAIK. There are two 'Calling Number' IEs (0x6c) and the second one should have been a 'Called Number' IE (0x70) instead ('190341' is the number you dialed, right?).

No, that's actually fine - the first number is user-provided("user number not screened") as it is a "location independent corporate number", the second one is the "network provided" regional number(Which i missed to obfuscate). After talking with a colleague who is very proficient with ISDN and testing the line with a ISDN testing device today, we came to the conclusion that ftdm sends "CALL PROCEEDING" immediately, instead of sending an "SETUP ACK" and waiting for additional digits. What it comes down to, i simply didn't allow overlap-dialing. This was easy to fix for the Sangoma card by setting the "overlap"-parameter to "yes", as documented in http://wiki.freeswitch.org/wiki/FreeTDM#FreeSWITCH_FreeTDM_configuration. However, on my second device, which has a HFC-S based card(OpenVOX B100P) installed, ftmod_libpri based, overlap-dialing doesn't seem to work. The debug-logs posted above are from this card. Googling for overlap-dialing with libpri brought up this thread from Dec 2010, where Michael Collins says it's not supported yet: http://lists.freeswitch.org/pipermail/freeswitch-users/2010-December/066695.... I assume this status has not changed? Best regards, Christian