[Asterisk-Dev] IAXtel Status
F.S.Salloum
ssal at intracom.gr
Mon Nov 29 00:20:04 MST 2004
Dear all,
Even if the question was not made to me, the only problem I
Had (and still have) with SER and Asterisk is regarding the Supervised
Transfer which doesn't work.
The problem is that Asterisk hasn't in his memory (iflist) the
Sip Session which is being established with the null INVITE before the REFER
message, since it is only stored in SER.
>From a search in google, I have found that one way to override this
Problem is by using a SER--> ASTERISK --> SER architecture but this
Is not so robust!
(http://mail.iptel.org/pipermail/serusers/2004-September/011637.html)
If this is solved then 100% SER is a great companion with Asterisik, since
everyone who has checked the code of SER and Asterisk (regarding the SIP
stuff) can fully understand that SER is superior and more RFC compatible.
Thanks
Sotiris
Updated news about the VoIP revolution
www.VOIPJournal.com
-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Tracy R Reed
Sent: Monday, November 29, 2004 8:45 AM
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] IAXtel Status
On Mon, Nov 29, 2004 at 01:27:52AM -0500, Jeremy McNamara spake thusly:
> Since when does SER talk IAX? IMHO, it sucks for SIP, so I would hate
> to see how they could bastardize an IAX implementation.
I have seen you pan SER a number of times now. Could you share with us
what is wrong with it? I have been told by a number of people running big
asterisk installations that you really need SER to make asterisk scale
with SIP. And if SER needed IAX I would hope they could just copy
asterisk's code. That is why we make things GPL.
--
Tracy Reed http://copilotcom.com
This message is cryptographically signed for your protection.
Info: http://copilotconsulting.com/sig
More information about the asterisk-dev
mailing list