8 Feb
2008
8 Feb
'08
1:40 p.m.
Hello,
Frank Durda IV wrote:
Stefan Sayer wrote:
I guess it is a performance issue - there is a little performance
penalty introduced, as it needs to open a socket for every outgoing
message just to see which socket to use.
If you look at ser-oob.cfg mhomed=yes is there (but greyed out).
Hello again,
I think I understand well your network setup now ;)
mhomed=yes
(general config option), then it will detect on which interface to send
out the message.
mhomed=yes was the final missing bit, and now packets emitted from
any interface from SER have a reasonable sender IP address in the
packet and payload. This got a call from the SIP phone to the PSTN
switch and got a call established (no audio), so 80 points there.
It is an interesting question as to why that isn't the default or
at least included in the samples, as it should be harmless on a
system with only one interface but would avoid confusion if a system
had two or more interfaces, even if one was purely for managament
and the other for all SIP/VOIP related communications.
Now we shall puzzle as to why mediaproxy doesn't seem to have done
anything, with the SIP phone and PSTN gateway still trying to send
RTP packets direct to one another, something that doesn't work as the
two networks don't meet. We will go off and ponder why
the proxy addresses didn't get patched into the SIP messages.
good luck!
Stefan
Thanks again to all who responded!
Frank
--
Stefan Sayer
VoIP Services
stefan.sayer(a)iptego.com
www.iptego.com
iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann