[Serusers] user permission problem on ser-jabber gw

[Daniel-Constantin MIERLA]

Hello,
did you check the message flow between ser and Jabber server to see 
whether the SIP message was delivered to Jabber server? Also, check the 
log messages when that happens (enable log_stderror and set debug to a 
high level - 9) and send me that part if some error message occurs. Tell 
me whether SIP messenger shows that the SIP message was not successfully 
delivered.

Regards,
Daniel


Toni Barata (EPS) wrote:

> Hi Daniel,
>  
> Ok, I found a configuration error on ser.cfg. On the Jaddress 
> parameter the Ip address had a sintax error (one of the dots was 
> replaceded by a comma).
> But now there is another problem:
>     - When the sip client (messenger) sends a IM to the Jabber client, 
> the jabber client  do not receive the message but he is "notified" 
> that the sip-client is on-line.
>     - When the jabber client send an IM to the sip client the messages 
> is received by the sip client.
>  
> Any idea of what is going on?
>  
> Best regards,
> Toni
>  
>
>     -----Original Message-----
>     From: Daniel-Constantin MIERLA [mailto:mierla at fokus.fraunhofer.de]
>     Sent: sexta-feira, 31 de Janeiro de 2003 18:30
>     To: Toni Barata (EPS)
>     Subject: Re: [Serusers] user permission problem on ser-jabber gw
>
>     You have to set debug=9 and log_stderror=yes in ser's config file.
>     Debug messages will be displayed on console and you can copy/paste
>     in a file.
>
>     If you got that error message, means that ser-jabber gw was
>     connected to Jabber server, but something was happening and the
>     connection was broken. So some messages should have been exchanged
>     between ser and Jabber. Did you check all your network interfaces
>     (I told you in last mail you have to sniff loopback interface if
>     Jabber server and ser is on the same machine)?
>
>     Regards,
>     Daniel
>
>     Toni Barata (EPS) wrote:
>
>>     Hi,
>>      
>>     I forgot to tell you that I put the ethereal sniffing the network
>>     and  no packet was sent by the ser-jabber gw to the port 5222 on
>>     the jabber server.
>>     I seems that this is an internal problem on the ser-jabber. Is
>>     there a way to send the logs to a file?
>>      
>>     Best regards,
>>     Toni
>>
>