[Users] Re: registering problems when using TLS

Marco Teixeira marcoteixeira at vipvoz.com
Tue Mar 28 11:35:23 CEST 2006


Hi,

Beware that if you're running openser without fork (usually for debugging), 
it will only bind your first defined ip address.
In this case, udp: XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX]:5060.
So, you might want to netstat port 5061 to confirm it is binded to openser.

Regards

Marco


"Joao Pereira" <joao.pereira at fccn.pt> escreveu na 
mensagem news:44281016.7090203 at fccn.pt...
> No, the phone is in a differente machine.
> I believe the problem is in the ports OpenSER is using. That are:
>
> Listening on
>             udp: XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX]:5060
>             tcp: XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX]:5060
>             tls: XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX]:5061
>
> Is this the correct configuration when using TLS?
> The SIP clients should use 5060 to register. And the OpenSER should use 
> 5061 to route calls between SIP servers?
> Thanks
> Joao
>
>
>
>
> Cesc wrote:
>
>>One option ...
>>do you run the phone and server on the same machine? they may be
>>listening on the same port or something like that ... that is, the
>>phone sends to the server and the server replies to the contact
>>address ... which is in fact the server address (the phone didn't tell
>>you about the port conflict ... too bad :D ). So, you get a loop.
>>
>>Cesc
>>
>>On 3/27/06, Joao Pereira <joao.pereira at fccn.pt> 
>>wrote:
>>
>>>Hello to all
>>>Im using openser with TLS (1.0.1-tls) but when I try to register a
>>>client (X-Lite), the answer is always:
>>>"Too Many Hops"
>>>because of this:
>>>
>>>        if (!mf_process_maxfwd_header("10")) {
>>>                sl_send_reply("483","Too Many Hops");
>>>                exit;
>>>        };
>>>
>>>
>>>
>>>Whats the problem?
>>>Without TLS, this error doesnt happen.
>>>Thanks
>>>Joao Pereira
>>>
>>>_______________________________________________
>>>Users mailing list
>>>Users at openser.org
>>>http://openser.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>
> 







More information about the sr-users mailing list