Hey there,
Here are the syslog messages and ngrep for a serweb send message. Serweb reports message sent ok, but I don't receive it on the client, nor is it stored in the Message Store?
Any ideas would be very welcome!
Dave
MSILO: the downstream UA does not support MESSAGE requests ... Jul 20 08:49:49 sip /usr/sbin/ser[23058]: ACC: transaction answered: method=MESSAGE, i-uri=sip:admin@161.30.94.68, o-uri=sip:admin@161.30.94.70:5060, call_id=73f9fea9-0@127.0.0.1, from=sip:test1@sip.dev.inmarsat.com;tag=533cb9e91f4b999cf76861cbb9ed54ed -fba5, code=202 Jul 20 08:49:52 sip /usr/sbin/ser[23017]: ERROR: udp_send: sendto(sock,0xbd777de0,667,0,0xbd779394,16): Invalid argument(22) Jul 20 08:49:52 sip /usr/sbin/ser[23017]: CRITICAL: invalid sendtoparameters one possible reason is the server is bound to localhost and attempts to send to the net Jul 20 08:49:52 sip /usr/sbin/ser[23017]: msg_send: ERROR: udp_send failed Jul 20 08:49:52 sip /usr/sbin/ser[23017]: ERROR: t_forward_nonack: sending request failed Jul 20 08:49:52 sip /usr/sbin/ser[23017]: ACC: transaction answered: method=MESSAGE, i-uri=sip:daemon@mydomain.org, o-uri=sip:daemon@mydomain.org, call_id=73f9fea8-0@161.30.94.68, from=sip:sip_registrar@161.30.94.68;tag=533cb9e91f4b999cf76861cbb9ed54ed -1247, code=477
ngrep UDP port 5060 interface: eth0 (161.30.94.64/255.255.255.224) filter: ip and ( port 5060 ) match: UDP ########################### U 161.30.94.68:5060 -> 161.30.94.70:5060 MESSAGE sip:admin@161.30.94.70:5060 SIP/2.0..Max-Forwards: 10..Record-Route : <sip:admin@161.30.94.68;ftag=533cb9e91f4b999cf76861cbb9ed54ed-fba5;lr=on
..Via: SIP/2.0/UDP 161.30.94.68;branch=z9hG4bK33b2.acca75b7.0..Via: SIP/2.0 /UDP 161.30.94.68;branch=z9hG4bKb789.54d3c0e.0..To: <sip:admin@161.30.94.68
..From:
sip:test1@sip.dev.inmarsat.com;tag=533cb9e91f4b999cf76861cbb9ed54e d-fba5..CSeq: 10 MESSAGE..Call-ID: 73f9fea9-0@127.0.0.1..Content-Length: 16 ..User-Agent: Sip EXpress router(0.8.12 (i386/linux))..p-version: Web_inter face_Karel_Kozlik-0.9..Contact: sip:daemon@mydomain.org..Content-Type: te xt/plain; charset=UTF-8....test message.... ## U 161.30.94.70:5060 -> 161.30.94.68:5060 SIP/2.0 405 Method Not Allowed..Via: SIP/2.0/UDP 161.30.94.68;branch=z9hG4b K33b2.acca75b7.0..Via: SIP/2.0/UDP 161.30.94.68;branch=z9hG4bKb789.54d3c0e. 0..From: sip:test1@sip.dev.inmarsat.com;tag=533cb9e91f4b999cf76861cbb9ed54e d-fba5..To: sip:admin@161.30.94.68;tag=3946696931..Contact: sip:admin@16 .30.94.70:5060..Call-ID: 73f9fea9-0@127.0.0.1..Allow: INVITE,ACK,BYE,CANC EL,OPTIONS,NOTIFY..CSeq: 10 MESSAGE..Server: X-Lite release 103m..Content- Length: 0.... #exit 31 received, 0 dropped
-----Original Message----- From: Andrei Pelinescu-Onciul [mailto:pelinescu-onciul@fokus.fraunhofer.de] Sent: 19 July 2004 15:37 To: Dave Bath Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Problem with messages + msilo
On Jul 19, 2004 at 13:32, Dave Bath dave@fuuz.com wrote:
Hey there,
Once again, many thanks for a swift response Andrei! No, the machine does not have two interfaces, it's a single public ip address. What do you mean about ingress filtering? Which network dumps would be
helpful?
If it's a single ip, than don't worry about ingress filtering. Just dump the udp traffic to your machine port 5060 until you get one of the log error message (sendto ...) and then send use the log and the dump. The message might also be caused by some UA using a 0 source port (which is highly broken), or a 0 destination port or ip in the message uri.
Andrei