Yes this is a big no no, forgive my ignorance I understand using SER as a proxy but if you are dealing with one server why run both SER and Ast? It's most likely confused because of the callid being the same. If you *really* wanted to you could media proxy via SER and potentially generate a second callid.. I tried doing this myself in a similar situation and realized it's more a pain than it's worth..
-----Original Message----- From: Alexander Hoffmann [mailto:alexander.hoffmann@netgenius.de] On Friday 14 January 2005 12:53, Klaus Darilion wrote:
What does hairpin in asterisk terminology mean?
Thus it is absolutely ok if there is an INV from ISDN card1 -> going to SER -> returning to * -> terminated at ISDN card2. You can easily configure * to route calls like this, but it will complain about loops. If you comment out the loop detection in the source code (because this is not a loop here) then Asterisk will run into a deadlock. I googled for a solution and saw people discussing similar issues and talking about hairpins. IMHO: What ever you call this, it stays a bug in ASTERISK. If you have any suggestions what to do, please let me know !
Thanks, Alex
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
The reason why I need both is: 1) I want to use SER as the only point where to implement all call routing logic 2) I need a gateway that supports ISDN NT-mode
Because of 2 I am using Asterisk, do you know something better ?
Regards, Alex
On Tuesday 18 January 2005 02:03, Matt Schulte wrote:
Yes this is a big no no, forgive my ignorance I understand using SER as a proxy but if you are dealing with one server why run both SER and Ast? It's most likely confused because of the callid being the same. If you *really* wanted to you could media proxy via SER and potentially generate a second callid.. I tried doing this myself in a similar situation and realized it's more a pain than it's worth..
-----Original Message----- From: Alexander Hoffmann [mailto:alexander.hoffmann@netgenius.de]
On Friday 14 January 2005 12:53, Klaus Darilion wrote:
What does hairpin in asterisk terminology mean?
Thus it is absolutely ok if there is an INV from ISDN card1 -> going to SER -> returning to * -> terminated at ISDN card2. You can easily configure * to route calls like this, but it will complain about loops. If you comment out the loop detection in the source code (because this is not a loop here) then Asterisk will run into a deadlock. I googled for a solution and saw people discussing similar issues and talking about hairpins. IMHO: What ever you call this, it stays a bug in ASTERISK. If you have any suggestions what to do, please let me know !
Thanks, Alex
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Alexander Hoffmann -
Matt Schulte