[Serusers] SER talks SIP to Jabber Server

[Délio Filipe Russo Guerra]

Daniel, here is the log file you requested, and thanks for 
the time you are spending helping me.
About de DNS issue, i have an entry in /etc/hosts like 
this:
192.168.89.25           im.ptinovacao.pt 
msn.im.ptinovacao.pt icq.im.ptinovacao.pt 
yahoo.im.ptinovacao.pt aim.im.ptinovacao.
pt

so i don't see the problem resolving host names...


PS. sorry about the size of the ethereal network dump.

Délio Guerra
IT - Instituto de Telecomunicações
Universidade de Aveiro - Portugal

On Tue, 02 Mar 2004 21:48:24 +0100
  Daniel-Constantin Mierla <daniel at iptel.org> wrote:
>
>I would need to see some debug messages, too. Set debug=9 
>and log_stderror=yes in ser config file and run again. 
>Send me the the debug messages you get in console.
>
>Do you have all hostnames for jabber gateway in DNS. 
>After receiving a message from a Jabber user MSN 
>messenger starts using the Record Routing. So next 
>messages have Route headers and the next statement you 
>have in your config file
>
>    if (loose_route()) {
>        t_relay();
>        break;
>    };
>
>sends the request further before hitting the Jabber 
>processing part. If you would have the hostnames in DNS 
>then the request should be sent via loopback to itself. I 
>need those debug messages to find out more.
>
>.Daniel
>
>PS. Filtering only sip traffic reduces the size of 
>network dump a lot (for example, set filter to <port 
>5060>)
>
>On 3/2/2004 5:16 PM, Délio Filipe Russo Guerra wrote:
>
>>Here are the requested network dumps (ethereal network 
>>dumps), and the 
>>ser.cfg file in case you need to see the configuration 
>>used.
>>
>>to make things more readable:
>>  user1 (SIP client) IP: 10.112.64.239
>>  user2 (Jabber client) IP: 10.112.64.121
>>  SER (SIP Express Router) IP: 10.112.64.121
>>  Jabber Server IP: 192.168.89.25
>>
>>thanks in advance,
>>
>>Délio Guerra
>>IT - Instituto de Telecomunicações
>>Universidade de Aveiro - Portugal
>>
>>On Tue, 02 Mar 2004 17:02:03 +0100
>> Daniel-Constantin Mierla <daniel at iptel.org> wrote:
>>
>>>Please send me some network dumps. I will check them.
>>>
>>>.Daniel
>>>
>>>On 3/2/2004 4:25 PM, Délio Filipe Russo Guerra wrote:
>>>
>>>>I'm having a problem putting jabber gateway to work. I'm 
>>>>using SER 
>>>>0.8.12 and microsoft messenger 4.7 as a SIP client and 
>>>>PSI as a 
>>>>Jabber client.
>>>>
>>>>I had configured the jabber gateway in ser.cfg and i can 
>>>>talk 
>>>>between the to clients (at least for a while).
>>>>
>>>>I'm using user1 as both SIP client and jabber client, and 
>>>>user2 as a 
>>>>jabber client only. So the SIP address for the user1 is 
>>>>sip:user1 at sipserver.sipdomain. user1 also have an jabber 
>>>>account 
>>>>user1 at jabberserver.jabberdomain. user2 as an jabber 
>>>>account 
>>>>user2 at jabberserver.jabberdomain.
>>>>
>>>>I start to talk from user1 (microsoft messenger logged in 
>>>>SIP 
>>>>server) to user2 (PSI logged in jabber server) and it 
>>>>works just 
>>>>fine. If i continue to talk in this direction i have no 
>>>>problems.
>>>>
>>>>When i start to talk from user2 (PSI logged in jabber 
>>>>server) to 
>>>>user1 (microsoft messenger logged in SIP server)
>>>>i have no problems either.
>>>>
>>>>The problem appears when i want to talk again from user1 
>>>>to user2... 
>>>>that is, when i receive the first response from user2 -> 
>>>>user1 it 
>>>>blocks the way user1 -> user2.
>>>>
>>>>I've put a sniffer to find out why this appened, and 
>>>>appears that 
>>>>after user2 responds, all the events (Ex: INFO for 
>>>>Keyboard 
>>>>Activity) or messages from user1->user2 are SIP to jabber 
>>>>server. It 
>>>>seams that SER is not using the jabber gateway.
>>>>
>>>>Can anyone help me please...
>>>>Délio Guerra
>>>>IT - Instituto de Telecomunicações
>>>>Universidade de Aveiro - Portugal
>>>>
>>>>_______________________________________________
>>>>Serusers mailing list
>>>>serusers at lists.iptel.org
>>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>>
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ser_log_file.tar.gz
Type: application/x-gzip
Size: 5474 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040303/4db04d0b/attachment.bin>