[Home]

Summary:ASTERISK-01259: asterisk will native bridged trunked iax to non trunked iax which doesn't work
Reporter:revk (revk)Labels:
Date Opened:2004-03-21 12:06:48.000-0600Date Closed:2011-06-07 14:05:13
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:From comments on report 0001054 it is clear asterisk does not allow a trunked iax link at one and and a non trunked iax link at the other. If you get a call that is non trunked (e.g. guest@) and it is routed to a trunked iax link, it does native bridging iax to iax and then the end say our of trunk space and drop the call!

****** ADDITIONAL INFORMATION ******

Is it possible to configure differently? Or make asterisk cope with trunked at one end and not at the other? Or make it not try and make a native bridge when it knows it wont work!
Comments:By: Olle Johansson (oej) 2004-04-12 04:23:18

Is this still a problem?

By: revk (revk) 2004-04-12 05:39:33

I have configured around it for now, so not seeing it at present.
Has something been fixed?

I can try and reproduce it again with the latest stable cvs if you like.,

By: zoa (zoa) 2004-04-12 06:31:40

how did you configure around it ?

By: revk (revk) 2004-04-12 06:35:10

With careful dialplans and enum configurations. The main problem was that I have some numbers on an asterisk box in London and some in Bracknell. I had set the enum routing to be to London (iax, guest login, not trunked), and it would know some numbers are handled by Bracknell and forward there (iax, authenticated, trunked). The two IAX connections would be bridged by the London box (joining an non trunked to a trunked IAX link) and the call drops immediately with out of trunk space. I have configured specific entries in enum to go direct to bracknell to avoid the forwarding.

By: twisted (twisted) 2004-04-29 10:01:34

According to ASTERISK-1048 this has been fixed in cvs, therefore I'm closing this bug.  If this is still an issue, please re-open or file a new bug report.

Thanks!