AW: [Asterisk-Dev] Passing overlap digits from one pri-E1 to another

[Thomas Haeger]

Hi Peter, hi Feleix,

which revision you are using ? Is it the "v1-0_stable" ?
I think this problem was fixed in the "head" revision.

See  http://bugs.digium.com/bug_view_page.php?bug_id=0001080.

How ever, i'am wondering about the bug politics in CVS.... i think it's
better to fix those bugs in the "stable" branch too, because it's really a
BUG.


Best regards,

Thomas.

-----Ursprungliche Nachricht-----
Von: asterisk-dev-admin at lists.digium.com
[mailto:asterisk-dev-admin at lists.digium.com]Im Auftrag von ePyron Felix
Deierlein
Gesendet: Donnerstag, 10. Juni 2004 09:30
An: asterisk-dev at lists.digium.com
Betreff: RE: [Asterisk-Dev] Passing overlap digits from one pri-E1 to
another


Hello Peter,

does it work with your changes? If yes, could you send a diff-file?
We have the same problems in germay...


Thanks


Felix

> -----Original Message-----
> From: asterisk-dev-admin at lists.digium.com
> [mailto:asterisk-dev-admin at lists.digium.com] On Behalf Of
> Peter Svensson
> Sent: Wednesday, June 09, 2004 11:29 PM
> To: asterisk-dev at lists.digium.com
> Subject: [Asterisk-Dev] Passing overlap digits from one
> pri-E1 to another
>
> In Sweden overlap dialing is the norm due to our varying
> length phone numbers. I am currently interfacing asterisk to
> our telco and our existing pbx through two E1 links off a
> TE405P. The pbx sends all digis as single overlap digits
> regardless of how they are dialed.
>
> Most things work as expected. However, there seems to be a
> problem with overlap digits. We have an extension
>   exten => 0,1,Dial(Zap/g1)
> that sends the connection from the pbx to an outside line
> immediatly. This works, but no further digits are passed.
> After a bit of sifting through the source I found that the
> INFORMATION elements from the pbx are stopped in
> libpri/q931.c q931_receive() by the following test:
>
>   if (c->ourcallstate!=Q931_CALL_STATE_OVERLAP_RECEIVING)
>       break;
> After the dial command is executed the digits are dropped
> since ourcallstate==Q931_CALL_STATE_INCOMING_CALL_PROCEEDING.
>
> I have tried allowing that state as well and this seems to
> work. Is this the correct way to solve this?
>
> Another problem occurs when the pbx sends a long dialstring
> by itself.
> There is a window between deciding which extension to use and
> having seized the b channel and set up the call. Incoming
> digits during this interval are neither remembered nor passed
> to the outgoing channel by app_dial.
>
> Peter
> --
> Peter Svensson      ! Pgp key available by finger, fingerprint:
> <petersv at psv.nu>    ! 8A E9 20 98 C1 FF 43 E3  07 FD B9 0A 80 72 70 AF
> --------------------------------------------------------------
> ----------
> Remember, Luke, your source will be with you... always...
>
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>

_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev