Re: [Serusers] Ser + Asterisk on the same box??

Your problems seems to be concerned to the RTP part of the comunication... as SIP pointed, where should the clients send the RTP traffic? To 127.0.0.1 (Your Asterisk IP)? I don't think so... ;) So, from what I see and understand from Your explanation, You have two choices: 1- bind Asterisk to an external IP like SER (can be the same IP), but in another port; 2- try to include in Your design a RTP-Proxy application (rtproxy or mediaproxy are good choices). Edson. > -----Original Message----- > From: serusers-bounces(a)lists.iptel.org [mailto:serusers- > bounces(a)lists.iptel.org] On Behalf Of John Breen > Sent: quinta-feira, 24 de maio de 2007 00:15 > To: SIP > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Ser + Asterisk on the same box?? > > SIP wrote: > >> Your biggest issue, bar none, is using the loopback address for >> anything externally-facing. 127.0.0.1 is called a loopback address for >> a reason -- it never leaves the host itself. Just how do you expect >> the SIP phones to be able to contact a 127.0.0.1 address when that >> address is, in essence, themselves? >> >> There's something inherently flawed in your design. >> >> Let's back up and explain, in detail, what it is exactly you're trying >> to do, and why you feel the 127.0.0.1 address should be part of this >> equation? Perhaps we can suggest something if we know what you're >> trying to do. >> >> > There's a very simple reason. Asterisk and SER are on the same > machine. So the traffic from SER to asterisk doesn't need to leave the > box. This is why I'm using the loopback interface - there's no need to > use the real world one. >