El Tuesday 04 September 2007 15:03:25 Dan escribió:
> Full ngrep log attached.


In the INVITE OpenSEr sends to your provider is appears:


  ## U 78.45.146.34:5060 -> 212.34.169.220:5060
  INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0.
  Record-Route: <sip:78.45.146.34;ftag=6613ce14;lr>.
  To: <sip:[EMAIL PROTECTED]>.
  From: 58.68.96.11<sip:[EMAIL PROTECTED]>;tag=6613ce14.
  Call-ID: 757a270529254e41.
  ...
  Contact: <sip:[EMAIL PROTECTED]:5060>   <---- **1**


But in the BYE from your provider it appears:


  ## U 212.34.169.220:5060 -> 78.45.146.34:5060
  BYE sip:[EMAIL PROTECTED] SIP/2.0.   <---- **2**
  Route: <sip:78.45.146.34;ftag=6613ce14;lr>.
  From: <sip:[EMAIL PROTECTED]>;tag=04093807084639921117967993.
  Call-ID: 757a270529254e41.
  To: 58.68.96.11<sip:[EMAIL PROTECTED]>;tag=6613ce14.
  ...

That is wrong, the **2** field should be the same as **1** in order to OpenSer 
route the BYE to EyeBeam. Because the URI is 78.45.146.34 (OpenSer's IP) then 
the BYE arrives to OpenSer, it reads "Route: 78.45.146.34" so it deletes 
the "Route" header and sends again the BYE to himself. But this time there is 
not a "Route" header so the message is NOT in dialog.

I htink you have deleted, by error, some of the trace messages after the BYE, 
maybe you though they were repeat messages (retransmited by timers and so).
Nooo, sorry, you don't see it in the trace because now it's localhost 
connection (not ethX).

Try again the trace but with -d any   (all the net devices, not just eth0).
  ngrep -d any -P ' ' -W byline -T -t "$*" udp port 5060




-- 
ilimit...


*Iñaki Baz Castillo*
[EMAIL PROTECTED]

ÀREA SISTEMES
0034 937 333 375
VOLTA 1, PIS 5
08224 TERRASSA.BCN

Aquest enviament és confidencial i està destinat únicament a la persona a qui 
s'ha enviat.
Pot contenir informació privada sotmesa al secret professional, la distribució 
de la qual està prohibida per la legislació vigent.

_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to