|Summary:||ASTERISK-03877: Data Calls through asterisk don't work|
|Date Opened:||2005-04-06 10:26:29||Date Closed:||2011-06-07 14:10:06|
after today 6.4.06 Upgrade to cvs head I couldn't make a Data call through asterisk anymore. In the version of lets say 2 or 3 days before it worked without problems (just cvs update).
My config is:
pppd --> BRI-ISDN (TRANSCAP UNRES DIG) --> cable --> BRI ISDN --> chan_misdn --> asterisk --> chan_misdn --> BRI ISDN (still TRANSCAP UNRES DIG) --> PSTN
The Frames are AST_FORMAT_ALAW and AST_FRAME_VOICE, is there any recent change which touches the voice data ?
|Comments:||By: Paul Cadach (pcadach) 2005-04-06 12:28:20|
Could you provide call traces (set verbose 3, pri debug span <x>, etc.) to see what is wrong?
By: Mark Spencer (markster) 2005-04-06 14:01:21
This says chan_misdn... that's not part of asterisk. Does this not involve zap at all?
By: crich (crich) 2005-04-06 15:08:41
thats not a zaptel nor chan_zap problem at all. It must have to do with asterisk frame forwarding concept, since it works against asterisk stable and head release of some days ago.
chan_misdn uses the hdlc controller of the connected isdn cards, so it doesn't get the data as 8khz stream, instead it gets every single frame asyncronous. This was no problem before, chan_misdn queued them as voice frame and it worked ..
I think it would be a good idea to have something like AST_FRAME_DATA to send hdlc decoded frames through the asterisk.
thanks for your help, I'd like to find out whats wrong... tommorrow I'll try some further tests
PS: markster i think this should involve zap too, but i couldn't test yet.
By: Mark Spencer (markster) 2005-04-06 15:15:15
Since chan_misdn is not a part of Asterisk, we do not support it though this bug tracker. If the author of chan_misdn will disclaim the code, we can add it to Asterisk and then reopen this issue.