[Serusers] How SER communicate to other SIP server
roayu
roayu at ctisys.net
Mon Jul 9 10:12:36 CEST 2007
Hi, Olaf!
I managed to call to the other SIP server. Unfortunately, both sides can't
hear anything. What could be the problem? Could it be the NAT issue? If so,
where should I allocate them to use the mediaproxy(before/after
rewritehostport())?
Thanks.
Best regards,
Roa Yu
-----Original Message-----
From: Olaf Bergmann [mailto:Olaf.Bergmann at freenet-ag.de]
Sent: Wednesday, July 04, 2007 2:14 PM
To: roayu
Cc: serusers at lists.iptel.org
Subject: Re: [Serusers] How SER communicate to other SIP server
roayu wrote:
> Hi, Olaf!
>
>>From what I understand about forward() is that it will forward the request
> to the given destination statelessly. Whereas for t_relay(), it will relay
a
> message to the destination stated in current URI statefully. How do I get
> the URI to point to the other SIP server by using t_relay() as I couldn't
> assign any IP address for t_relay(). I managed to assign an IP address by
> using forward().
>
> I tried to use both. Unfortunately, I still failed to forward the message
to
> the another SIP server to establish the call. Is there any functions I
need
> to use before using either those 2 functions? FYI, I will only call them
> when it starts to INVITE.
482 Loop Detected
The function you are looking for is called rewritehostport (or
rewritehost, if you like). But you could also use
t_relay_to_{udp,tcp} to specify a literal transport address where
you want your request being routed to.
<http://www.iptel.org/ser/doc/search> gives more information on
these functions.
Regards,
Olaf
More information about the sr-users
mailing list