[Serusers] Problem with messages + msilo

[Dave Bath]

Daniel,

many thanks for swift response!. If I set fork=yes I get the same error.
If I set listen=<ip> then strange things break.. calls are no longer
connected properly, and UAs cant log in.  

Any more suggestions?!

D

-----Original Message-----
From: Daniel-Constantin Mierla [mailto:daniel at iptel.org] 
Sent: 16 July 2004 22:34
To: Dave Bath
Cc: serusers at lists.iptel.org
Subject: Re: [Serusers] Problem with messages + msilo

Do you have fork=yes in your config file? If no, then either set 
fork=yes or set the public ip explicitly to listen to with: 
listen=ip_address.

Daniel


On 07/16/04 23:22, Dave Bath wrote:

>I don't know!  I have perhaps misunderstood... it is not explicitly
>bound to anything.  It is a single machine with a single network card
>with a single external Ip address?
>
>D
>
>-----Original Message-----
>From: Daniel-Constantin Mierla [mailto:daniel at iptel.org] 
>Sent: 16 July 2004 22:16
>To: Dave Bath
>Cc: serusers at lists.iptel.org
>Subject: Re: [Serusers] Problem with messages + msilo
>
>Hello,
>there is a self explanatory error message -- is it the case?
>
>On 07/16/04 18:26, Dave Bath wrote:
>
>  
>
>>Hey guys,
>>
>>I have been battling with msilo, and the routing logic. It finally 
>>looks like it might be beginning to get there, (ser actually restarts 
>>now!) lol, but I have a problem when I try and send a message.
>>
>>I am using the serweb utility to try and send to "sip:admin@<ip>" and 
>>it reports "message accepted for delivery"... but I don't receive it. 
>>Checking the log shows;
>>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20227]: MSILO: the downstream UA 
>>does not support MESSAGE requests ...
>>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20227]: ACC: transaction answered: 
>>method=MESSAGE, i-uri=sip:admin at 161.30.94.68, 
>>o-uri=sip:admin at 81.86.136.86:5060, call_id=7971f97d-0 at 127.0.0.1, 
>>
>>    
>>
>from=sip:admin at sip.dev.inmarsat.com;tag=533cb9e91f4b999cf76861cbb9ed54e
d
>-79e5, 
>  
>
>>code=202
>>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20187]: ERROR: udp_send: 
>>sendto(sock,0xbd70f700,671,0,0xbd70e1dc,16): Invalid argument(22)
>>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20187]: CRITICAL: invalid 
>>sendtoparameters one possible reason is the server is bound to 
>>localhost and attempts to send to the net
>>
>>    
>>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>Daniel
>
>  
>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20187]: msg_send: ERROR: udp_send
>>    
>>
>failed
>  
>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20187]: ERROR: t_forward_nonack: 
>>sending request failed
>>
>>Jul 16 17:20:01 sip /usr/sbin/ser[20187]: ACC: transaction answered: 
>>method=MESSAGE, i-uri=sip:admin at 161.30.94.68, 
>>o-uri=sip:admin at 81.86.136.86:5060, call_id=7971f97d-0 at 161.30.94.68, 
>>
>>    
>>
>from=sip:sip_registrar at 161.30.94.68;tag=533cb9e91f4b999cf76861cbb9ed54e
d
>-8a85, 
>  
>
>>code=477
>>
>>Any ideas?
>>
>>Many thanks again, and thanks for a brilliant list!
>>
>>Dave
>>
>>----------------------------------------------------------------------
-
>>    
>>
>-
>  
>
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>> 
>>
>>    
>>
>
>
>
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
>  
>