Dear Mr Knan
I checked with 5060 port with snom's advanced setting
but same
problem , 404
now i am checking with the dial plan of OnDo sip server and
setting with
differeent routing .
thanks
tapan
On 4/26/07, Rayees Khan <rayees.khan digitalk.com> wrote:
>
>
> If you log onto the phone via a browser. Browse to
Advanced Network in
> Advance settings. Set the Network Identity (port) to
5060, that would get
> rid of this problem to begin with.
> 224.0.1.75 is SIP multicast address. It seems that your
phone is
> configured to use muticast. I guess your phone needs
changes in settings and
> a reboot 
>
>
> regards
> Rayees
>
>
> ------------------------------
> *From Tapan
krishna Biswal [mailto:tapan.carcgmail.com]
> *Sent Thursday,
April 26, 2007 4:05 PM
> *To Rayees
Khan
> *Cc Sarkar,
Uttam; sip-implementorscs.columbia.edu
> *Subject Re:
[Sip-implementors] 404 Not Found
>
>
> Dear Mr Khan
>
> For REGISTRATION
PART
> A. Now i check once again the REGISTRATION
process of the SNOM
> phone.
> And all the messaging is happening at 2051
port.( it is varing for
> the different REGISTRATIOn.)
> Secondly After getting the 401 UnAuth. from server ,
it sending it MAC
> addresslocalhost to some other ip like 224.0.1.75. ( what ip
is this )
> Then after it is getting 200 Ok from the OnDO SIP
server.
>
>
> thanks
>
> tapan
>
>
>
>
>
>
>
>
> On 4/26/07, Rayees Khan <rayees.khandigitalk.com > wrote:
> >
> >
> > Hi Tapan,
> >
> > I did have a look at the Snom again and forced an
INVITE to it without
> > the line ID parameter. It does respond to the same
with 180, which means it
> > is OK with request without the lineid parameter.
> > So I had alook at your traces again. Assuming that
the first INVITE is
> > from XLite to OnDo and the second one is from OnDo
to Snom. The request line
> > in the second INVITE (going to SNOM) seems a bit
odd to me because of the
> > port 2072. Is that what the phone is registered as
with OnDo?
> >
> > regards
> > Rayees
> >
> >
> >
> >
> > ------------------------------
> > *From Tapan
krishna Biswal [mailto:tapan.carcgmail.com]
> > *Sent Thursday,
April 26, 2007 2:33 PM
> > *To Rayees
Khan
> > *Cc Sarkar,
Uttam; sip-implementorscs.columbia.edu
> > *Subject Re:
[Sip-implementors] 404 Not Found
> >
> >
> > Ok Mr Khan/Uttam
> >
> > Could you please tell me how to
configure the X-lite ,
> > so that it can send the INVITE request containing
the required "line" part.
> >
> > And yes i would like to tell all
of you that ..
> > 1.In OnDo sip server, i have created user
acount for the
> > corresponding users( User Authenication part )
> > 2. After getting registred of the snom 360 and
X-lite , the OnDo
> > SIP server automatically displaying contact uri at
Registed Client.
> >
> > Hence i do not know to configure
X-lite or OnDo server, so
> > that the INVITE request should contain the line
..
> >
> > And for different REGISTRATION
of SNOM 360 there are
> > different line , hence it creating one more
problem.
> >
> >
> >
> > thanks
> >
> > Tapan
> >
> > On 4/26/07, Rayees Khan <rayees.khandigitalk.com > wrote:
> > >
> > >
> > > That is correct. SNOM does send line ID as a
parameter in the contact
> > > when it registers with registrar.
> > > Contact: <sip:user10.1.3.205:5060;line=819ctzmd>;flow-id=1;q=1.0;
> > >
+sip.instance="<urn:uuid:57e98536-e146-4d1e-85ea-9fe
cb3d517dd>"
> > > This lineID is expected to be present in the
request line for any
> > > INVITE. If this is missing it moarns about
the ID not being found. The
> > > INVITE request line should look like
> > >
> > > INVITE sip:user10.1.3.205:5060;line=819ctzmd SIP/2.0
> > >
> > >
> > > regards
> > > Rayees
> > >
> > >
> > > -----Original Message-----
> > > From: sip-implementors-bouncescs.columbia.edu
> > > [mailto: sip-implementors-bouncescs.columbia.edu ] On Behalf Of
> > > Sarkar,
> > > Uttam
> > > Sent: Thursday, April 26, 2007 12:36 PM
> > > To: Tapan krishna Biswal;
sip-implementorscs.columbia.edu
> > > Subject: Re: [Sip-implementors] 404 Not
Found
> > >
> > > I think when SNOM 360 register, it useses
"lineid" in the Contact.
> > > So,it
> > > might expect that information in the request
URI while it's receiving
> > > INVITE.
> > >
> > >
> > > -----Original Message-----
> > > From: sip-implementors-bouncescs.columbia.edu
> > > [mailto:sip-implementors-bouncescs.columbia.edu] On Behalf Of Tapan
> > > krishna Biswal
> > > Sent: Thursday, April 26, 2007 2:51 AM
> > > To: sip-implementorscs.columbia.edu
> > > Subject: [Sip-implementors] 404 Not Found
> > >
> > > Hi
> > >
> > > I get "404 Not Found " , when i
am making call from X-lite 3.0 SIP
> > > soft phone to SNOM 360.
> > >
> > > please find here the brief description
of my set up and
> > > configuration . the following are ......
> > >
> > > 1. brekeke SIP server
> > > ( where i have
created account for both snom
> > >
> > > user and X-lite user)
> > >
> > > 2. Snom 360 is able to make
call to X-lite, and the
> > > RTP
> > > is through.
> > >
> > > 3. But when making call from
X-lite to Snom 360 , i am
> > > getting 404 Not Found.
> > >
> > > here i am attaching logs
of the corresponding
> > > call.
> > >
> > >
> > >
> > >
> > >
> > > Session Initiation Protocol
> > >
> > > Request-Line: INVITE sip:ansuman172.16.10.124 SIP/2.0
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport
> > >
> > > Max-Forwards: 70
> > >
> > > Contact: < sip:subha172.16.10.102:23420>
> > >
> > > To: "ansuman"< sip:ansuman172.16.10.124>
> > >
> > > From: "subha"<sip:subha172.16.10.124 >;tag=2c36ec2f
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 INVITE
> > >
> > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, NOTIFY, MESSAGE,
> > > SUBSCRIBE, INFO
> > >
> > > Content-Type: application/sdp
> > >
> > > User-Agent: X-Lite release 1006e stamp 34025
> > >
> > > Content-Length: 236
> > >
> > > Message body
> > >
> > > Session Description Protocol
> > >
> > > Session Initiation Protocol
> > >
> > > Status-Line: SIP/2.0 100 Trying
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > >
> > > From: "subha"< sip:subha172.16.10.124>;tag=2c36ec2f
> > >
> > > To: "ansuman"< sip:ansuman172.16.10.124>
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 INVITE
> > >
> > > Server: Brekeke SIP Server rev.206
> > >
> > > Content-Length: 0
> > >
> > >
> > >
> > > Session Initiation Protocol
> > >
> > > Request-Line: INVITE sip:ansuman172.16.10.103:2072 SIP/2.0
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP
> > >
172.16.10.124:5060;rport;branch=z9hG4bKea0b654b8805bbce.1
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > >
> > > Max-Forwards: 69
> > >
> > > Contact: <sip:subha172.16.10.124:5060>
> > >
> > > To: "ansuman"< sip:ansuman172.16.10.124>
> > >
> > > From: "subha"< sip:subha172.16.10.124>;tag=2c36ec2f
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 INVITE
> > >
> > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, NOTIFY, MESSAGE,
> > > SUBSCRIBE, INFO
> > >
> > > User-Agent: X-Lite release 1006e stamp 34025
> > >
> > > Record-Route:
<sip:172.16.10.124:5060;lr>
> > >
> > > Content-Type: application/sdp
> > >
> > > Content-Length: 236
> > >
> > > Message body
> > >
> > > Session Description Protocol
> > >
> > > Session Initiation Protocol
> > >
> > > Status-Line: SIP/2.0 404 Not Found
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP 172.16.10.124:5060
;rport=5060;branch=
> > > z9hG4bKea0b654b8805bbce.1
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > >
> > > From: "subha" < sip:subha172.16.10.124 >;tag=2c36ec2f
> > >
> > > To: "ansuman" <sip:ansuman172.16.10.124>
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 INVITE
> > >
> > > Allow: INVITE, ACK, CANCEL, BYE, REFER,
OPTIONS, NOTIFY, SUBSCRIBE,
> > > PRACK, MESSAGE, INFO
> > >
> > > Allow-Events: talk, hold, refer
> > >
> > > Supported: timer, 100rel, replaces, callerid
> > >
> > > Content-Length: 0
> > >
> > >
> > >
> > > Session Initiation Protocol
> > >
> > > Status-Line: SIP/2.0 404 Not Found
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > >
> > > From: "subha" < sip:subha172.16.10.124>;tag=2c36ec2f
> > >
> > > To: "ansuman" <sip:ansuman172.16.10.124 >
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 INVITE
> > >
> > > Allow: INVITE, ACK, CANCEL, BYE, REFER,
OPTIONS, NOTIFY, SUBSCRIBE,
> > > PRACK, MESSAGE, INFO
> > >
> > > Allow-Events: talk, hold, refer
> > >
> > > Supported: timer, 100rel, replaces, callerid
> > >
> > > Content-Length: 0
> > >
> > >
> > >
> > >
> > >
> > > Session Initiation Protocol
> > >
> > > Request-Line: ACK sip:ansuman172.16.10.124 SIP/2.0
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport
> > >
> > > To: "ansuman" < sip:ansuman172.16.10.124>
> > >
> > > From: "subha"< sip:subha172.16.10.124>;tag=2c36ec2f
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 ACK
> > >
> > > Content-Length: 0
> > >
> > >
> > >
> > >
> > >
> > > Session Initiation Protocol
> > >
> > > Request-Line: ACK sip:ansuman172.16.10.103:2072 SIP/2.0
> > >
> > > Message Header
> > >
> > > Via: SIP/2.0/UDP
> > > 172.16.10.124:5060;rport;branch=
z9hG4bKea0b654b8805bbce.1
> > >
> > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > >
> > > To: "ansuman" < sip:ansuman172.16.10.124>
> > >
> > > From: "subha"< sip:subha172.16.10.124>;tag=2c36ec2f
> > >
> > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > >
> > > CSeq: 1 ACK
> > >
> > > Record-Route: <sip:
172.16.10.124:5060;lr>
> > >
> > > Content-Length: 0
> > >
_______________________________________________
> > > Sip-implementors mailing list
> > > Sip-implementorscs.columbia.edu
> > > https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
> > >
> > >
_______________________________________________
> > > Sip-implementors mailing list
> > > Sip-implementorscs.columbia.edu
> > > https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
> > >
> > >
____________________________________________________________
__________
> > > This email has been scanned by the
MessageLabs Email Security System.
> > > For more information please visit http://www.messagela
bs.com/email
> > >
____________________________________________________________
__________
> > >
> > >
> > >
> > >
> > >
------------------------------------------------------------
----------------------
> > >
> > > IMPORTANT The information contained in this
e-mail any
> > > attachments is intended only for the named
recipient and may be
> > > privileged or confidential.
> > >
> > > If you are not the intended recipient, please
notify us immediately
> > > on +44 (0)1908 425000 and do not disclose,
copy, distribute
> > > or take any action based on the contents of
this e-mail.
> > >
> > > You should understand and accept that, when
communicating with us
> > > by e-mail, it is not a totally secure
communication medium.
> > >
> > > We accept no liability for any direct,
indirect or consequential loss
> > > arising from any action taken in reliance on
the information contained
> > > in this e-mail and give no warranty or
representation as to its
> > > accuracy
> > > or reliability.
> > >
> > > DIGITALK has the facility to monitor and read
both incoming
> > > and outgoing communications by e-mail. In
line with industry efforts
> > > to reduce the proliferation of Un-Solicited
SPAM messages,
> > > DIGITALK uses various methods including
Reverse-DNS
> > > lookups and ban-lists to prevent malicious
content reaching our users.
> > >
> > >
> > > This message and any attachments has been
scanned for known
> > > viruses. However, we would advise you to
ensure the content is
> > > indeed virus free. We do not, to the extent
permitted by law, accept
> > > any liability (whether in contract,
negligence or otherwise) for any
> > > virus
> > > infection and/or external compromise of
security and/or breach of
> > > confidentiality in relation to transmissions
sent by e-mail.
> > >
> > > VAT No: GB 876 3287 81. Reg No: 3080801
> > > Place of Registration: England
> > > Registered Office Address: 2 Radian Court,
Knowlhill, Milton Keynes
> > >
------------------------------------------------------------
----------------------"
> > >
> > >
> > >
> >
> >
____________________________________________________________
__________
> > This email has been scanned by the MessageLabs
Email Security System.
> > For more information please visit http://www.messagela
bs.com/email
> >
____________________________________________________________
__________
> >
>
>
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email
>
____________________________________________________________
__________
>
_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
|
Dear Friends
Still i am struglling with call now i am
sending you all the
coloured traces , and everything looking right....but still
i am getting 404
not found message.
Here are the tracess...
------------------------------------------------------------
-----------------------------------------------------------
Unsuccessful Call from X-lite to Snom 360
------------------------------------------------------------
-----------------------------------------------------------
Internet Protocol, Src Addr: 172.16.10.102 (172.16.10.102),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 47258 (47258), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:ansuman172.16.10.124 SIP/2.0
Message Header
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:subha172.16.10.102:47258>
To: "ansuman"<sip:ansuman172.16.10.124>
From: "subha"<sip:subha172.16.10.124>;tag=1e44db13
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY,
MESSAGE, SUBSCRIBE,
INFO
Content-Type: application/sdp
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 328
Message body
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.102 (172.16.10.102)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
47258 (47258)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
Message Header
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport=472
58
From: "subha"<sip:subha172.16.10.124>;tag=1e44db13
To: "ansuman"<sip:ansuman172.16.10.124>
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 INVITE
Server: Brekeke SIP Server rev.206
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.103 (172.16.10.103)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:ansuman172.16.10.103:5060 SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.124:5060;rport;branch=z9hG4bKbbadfa87c87cbbce.1
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport=472
58
Max-Forwards: 69
Contact: <sip:subha172.16.10.124:5060>
To: "ansuman"<sip:ansuman172.16.10.124>
From: "subha"<sip:subha172.16.10.124>;tag=1e44db13
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY,
MESSAGE, SUBSCRIBE,
INFO
User-Agent: X-Lite release 1006e stamp 34025
Record-Route: <sip:172.16.10.124:5060;lr>
Content-Type: application/sdp
Content-Length: 328
Internet Protocol, Src Addr: 172.16.10.103 (172.16.10.103),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 404 Not Found
Message Header
Via: SIP/2.0/UDP 172.16.10.124:5060;rport=5060;branch=
z9hG4bKbbadfa87c87cbbce.1
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport=472
58
From: "subha" <sip:subha172.16.10.124>;tag=1e44db13
To: "ansuman" <sip:ansuman172.16.10.124>
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY,
SUBSCRIBE, PRACK,
MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces, callerid
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.102 (172.16.10.102)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
47258 (47258)
Session Initiation Protocol
Status-Line: SIP/2.0 404 Not Found
Message Header
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport=472
58
From: "subha" <sip:subha172.16.10.124>;tag=1e44db13
To: "ansuman" <sip:ansuman172.16.10.124>
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY,
SUBSCRIBE, PRACK,
MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces, callerid
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.102 (172.16.10.102),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 47258 (47258), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: ACK sip:ansuman172.16.10.124 SIP/2.0
Message Header
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport
To: "ansuman" <sip:ansuman172.16.10.124>
From: "subha"<sip:subha172.16.10.124>;tag=1e44db13
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 ACK
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.103 (172.16.10.103)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: ACK sip:ansuman172.16.10.103:5060 SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.124:5060;rport;branch=z9hG4bKbbadfa87c87cbbce.1
Via: SIP/2.0/UDP 172.16.10.102:47258
;branch=z9hG4bK-d87543-e8245577743e9968-1--d87543-;rport=472
58
To: "ansuman" <sip:ansuman172.16.10.124>
From: "subha"<sip:subha172.16.10.124>;tag=1e44db13
Call-ID: OWNlY2RjYTk1NmUyY2EwN2QwOGY2NmJkNjUzNzMxMjA.
CSeq: 1 ACK
Record-Route: <sip:172.16.10.124:5060;lr>
Content-Length: 0
------------------------------------------------------------
-------------------------x----------------------------------
-
Successful Call from Snom 360 to X-lite
------------------------------------------------------------
-------------------------x----------------------------------
-
Internet Protocol, Src Addr: 172.16.10.103 (172.16.10.103),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:subha172.16.10.124 SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport
From: "ansuman" <sip:ansuman172.16.10.124>;tag=7wrmnk350b
To: <sip:subha172.16.10.124>
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
Max-Forwards: 70
Contact: <sip:ansuman172.16.10.103:5060;line=7d4cfzzy>;flow-id=1
P-Key-Flags: resolution="31x13",
keys="4"
User-Agent: snom360/6.5.2
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY,
SUBSCRIBE, PRACK,
MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces, callerid
Session-Expires: 3600;refresher=uas
Min-SE: 90
Content-Type: application/sdp
Content-Length: 370
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.103 (172.16.10.103)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
Message Header
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
From: "ansuman" <sip:ansuman172.16.10.124>;tag=7wrmnk350b
To: <sip:subha172.16.10.124>
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
Server: Brekeke SIP Server rev.206
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.102 (172.16.10.102)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
47258 (47258)
Session Initiation Protocol
Request-Line: INVITE sip:subha172.16.10.102:47258
SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.124:5060;rport;branch=z9hG4bKbafa6ccfc93fcbce.1
(Proxy
server)
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
From: "ansuman" <sip:ansuman172.16.10.124>;tag=7wrmnk350b
To: <sip:subha172.16.10.124>
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
Max-Forwards: 69
Contact: <sip:ansuman172.16.10.124:5060;line=7d4cfzzy>;flow-id=1
P-Key-Flags: resolution="31x13",
keys="4"
User-Agent: snom360/6.5.2
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY,
SUBSCRIBE, PRACK,
MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces, callerid
Session-Expires: 3600;refresher=uas
Min-SE: 90
Record-Route: <sip:172.16.10.124:5060;lr>
Content-Type: application/sdp
Content-Length: 370
Internet Protocol, Src Addr: 172.16.10.102 (172.16.10.102),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 47258 (47258), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 180 Ringing
Message Header
Via: SIP/2.0/UDP 172.16.10.124:5060;rport=5060;branch=
z9hG4bKbafa6ccfc93fcbce.1
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
Record-Route: <sip:172.16.10.124:5060;lr> (X-Lite)
Contact: <sip:subha172.16.10.102:47258>
To: <sip:subha172.16.10.124>;tag=ad3bad43
From: "ansuman"<sip:ansuman172.16.10.124>;tag=7wrmnk350b
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.103 (172.16.10.103)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 180 Ringing
Message Header
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
Record-Route: <sip:172.16.10.124:5060;lr>
Contact: <sip:subha172.16.10.124:5060>
To: <sip:subha172.16.10.124>;tag=ad3bad43
From: "ansuman"<sip:ansuman172.16.10.124>;tag=7wrmnk350b
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.102 (172.16.10.102),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 47258 (47258), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 480 Temporarily Unavailable
Message Header
Via: SIP/2.0/UDP 172.16.10.124:5060;rport=5060;branch=
z9hG4bKbafa6ccfc93fcbce.1
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
To: <sip:subha172.16.10.124>;tag=ad3bad43
From: "ansuman"<sip:ansuman172.16.10.124>;tag=7wrmnk350b
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.103 (172.16.10.103)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 480 Temporarily Unavailable
Message Header
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
To: <sip:subha172.16.10.124>;tag=ad3bad43
From: "ansuman"<sip:ansuman172.16.10.124>;tag=7wrmnk350b
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 INVITE
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.103 (172.16.10.103),
Dst Addr:
172.16.10.124 (172.16.10.124)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: ACK sip:subha172.16.10.124 SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport
From: "ansuman" <sip:ansuman172.16.10.124>;tag=7wrmnk350b
To: <sip:subha172.16.10.124>;tag=ad3bad43
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 ACK
Max-Forwards: 70
Contact: <sip:ansuman172.16.10.103:5060;line=7d4cfzzy>;flow-id=1
Content-Length: 0
Internet Protocol, Src Addr: 172.16.10.124 (172.16.10.124),
Dst Addr:
172.16.10.102 (172.16.10.102)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
47258 (47258)
Session Initiation Protocol
Request-Line: ACK sip:subha172.16.10.102:47258
SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.16.10.124:5060;rport;branch=z9hG4bKbafa6ccfc93fcbce.1
Via: SIP/2.0/UDP
172.16.10.103:5060;branch=z9hG4bK-3inuljg1zq2k;rport=5060
From: "ansuman" <sip:ansuman172.16.10.124>;tag=7wrmnk350b
To: <sip:subha172.16.10.124>;tag=ad3bad43
Call-ID: 3c267118de2b-a11akvtozkpssnom360-000413236072
CSeq: 1 ACK
Max-Forwards: 69
Contact: <sip:ansuman172.16.10.124:5060;line=7d4cfzzy>;flow-id=1
Record-Route: <sip:172.16.10.124:5060;lr>
Content-Length: 0
On 4/26/07, Tapan krishna Biswal <tapan.carcgmail.com> wrote:
>
> Dear Mr Knan
>
> I checked with 5060 port with snom's advanced
setting but same
> problem , 404
>
> now i am checking with the dial plan of OnDo sip server
and setting with
> differeent routing .
>
> thanks
>
> tapan
>
>
> On 4/26/07, Rayees Khan <rayees.khandigitalk.com> wrote:
> >
> >
> > If you log onto the phone via a browser. Browse to
Advanced Network in
> > Advance settings. Set the Network Identity (port)
to 5060, that would get
> > rid of this problem to begin with.
> > 224.0.1.75 is SIP multicast address. It seems that
your phone is
> > configured to use muticast. I guess your phone
needs changes in settings and
> > a reboot
> >
> >
> > regards
> > Rayees
> >
> >
> > ------------------------------
> > *From Tapan
krishna Biswal [mailto:tapan.carcgmail.com]
> > *Sent Thursday,
April 26, 2007 4:05 PM
> > *To Rayees
Khan
> > *Cc Sarkar,
Uttam; sip-implementorscs.columbia.edu
> > *Subject Re:
[Sip-implementors] 404 Not Found
> >
> >
> > Dear Mr Khan
> >
> > For
REGISTRATION PART
> > A. Now i check once again the REGISTRATION
process of the SNOM
> > phone.
> > And all the messaging is happening at 2051
port.( it is varing
> > for the different REGISTRATIOn.)
> > Secondly After getting the 401 UnAuth. from
server , it sending it
> > MAC addresslocalhost to some other ip like
224.0.1.75. ( what ip is
> > this )
> > Then after it is getting 200 Ok from the OnDO
SIP server.
> >
> >
> > thanks
> >
> > tapan
> >
> >
> >
> >
> >
> >
> >
> >
> > On 4/26/07, Rayees Khan <rayees.khandigitalk.com > wrote:
> > >
> > >
> > > Hi Tapan,
> > >
> > > I did have a look at the Snom again and
forced an INVITE to it without
> > > the line ID parameter. It does respond to the
same with 180, which means it
> > > is OK with request without the lineid
parameter.
> > > So I had alook at your traces again. Assuming
that the first INVITE is
> > > from XLite to OnDo and the second one is from
OnDo to Snom. The request line
> > > in the second INVITE (going to SNOM) seems a
bit odd to me because of the
> > > port 2072. Is that what the phone is
registered as with OnDo?
> > >
> > > regards
> > > Rayees
> > >
> > >
> > >
> > >
> > > ------------------------------
> > > *From Tapan
krishna Biswal [mailto:tapan.carcgmail.com]
> > > *Sent Thursday,
April 26, 2007 2:33 PM
> > > *To Rayees
Khan
> > > *Cc Sarkar,
Uttam; sip-implementorscs.columbia.edu
> > > *Subject Re:
[Sip-implementors] 404 Not Found
> > >
> > >
> > > Ok Mr Khan/Uttam
> > >
> > > Could you please tell me how
to configure the X-lite
> > > , so that it can send the INVITE request
containing the required "line"
> > > part.
> > >
> > > And yes i would like to tell
all of you that ..
> > > 1.In OnDo sip server, i have created user
acount for the
> > > corresponding users( User Authenication part
)
> > > 2. After getting registred of the snom
360 and X-lite , the OnDo
> > > SIP server automatically displaying contact
uri at Registed Client.
> > >
> > > Hence i do not know to configure
X-lite or OnDo server, so
> > > that the INVITE request should contain the
line ..
> > >
> > > And for different
REGISTRATION of SNOM 360 there
> > > are different line , hence it creating one
more problem.
> > >
> > >
> > >
> > > thanks
> > >
> > > Tapan
> > >
> > > On 4/26/07, Rayees Khan <rayees.khandigitalk.com > wrote:
> > > >
> > > >
> > > > That is correct. SNOM does send line ID
as a parameter in the
> > > > contact
> > > > when it registers with registrar.
> > > > Contact: <sip:user10.1.3.205:5060;line=819ctzmd>;flow-id=1;q=1.0;
> > > >
> > > >
+sip.instance="<urn:uuid:57e98536-e146-4d1e-85ea-9fe
cb3d517dd>"
> > > > This lineID is expected to be present in
the request line for any
> > > > INVITE. If this is missing it moarns
about the ID not being found.
> > > > The
> > > > INVITE request line should look like
> > > >
> > > > INVITE sip:user10.1.3.205:5060;line=819ctzmd SIP/2.0
> > > >
> > > >
> > > > regards
> > > > Rayees
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: sip-implementors-bouncescs.columbia.edu
> > > > [mailto: sip-implementors-bouncescs.columbia.edu ] On Behalf Of
> > > > Sarkar,
> > > > Uttam
> > > > Sent: Thursday, April 26, 2007 12:36 PM
> > > > To: Tapan krishna Biswal;
sip-implementorscs.columbia.edu
> > > > Subject: Re: [Sip-implementors] 404 Not
Found
> > > >
> > > > I think when SNOM 360 register, it
useses "lineid" in the Contact.
> > > > So,it
> > > > might expect that information in the
request URI while it's
> > > > receiving
> > > > INVITE.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: sip-implementors-bouncescs.columbia.edu
> > > > [mailto:sip-implementors-bouncescs.columbia.edu] On Behalf Of Tapan
> > > >
> > > > krishna Biswal
> > > > Sent: Thursday, April 26, 2007 2:51 AM
> > > > To: sip-implementorscs.columbia.edu
> > > > Subject: [Sip-implementors] 404 Not
Found
> > > >
> > > > Hi
> > > >
> > > > I get "404 Not Found " ,
when i am making call from X-lite 3.0SIP
> > > > soft phone to SNOM 360.
> > > >
> > > > please find here the brief
description of my set up and
> > > > configuration . the following are
......
> > > >
> > > > 1. brekeke SIP server
> > > > ( where i have
created account for both
> > > > snom
> > > > user and X-lite user)
> > > >
> > > > 2. Snom 360 is able to
make call to X-lite, and the
> > > > RTP
> > > > is through.
> > > >
> > > > 3. But when making call
from X-lite to Snom 360 , i
> > > > am
> > > > getting 404 Not Found.
> > > >
> > > > here i am attaching
logs of the corresponding
> > > > call.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Request-Line: INVITE sip:ansuman172.16.10.124 SIP/2.0
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport
> > > >
> > > > Max-Forwards: 70
> > > >
> > > > Contact: < sip:subha172.16.10.102:23420>
> > > >
> > > > To: "ansuman"<
sip:ansuman172.16.10.124>
> > > >
> > > > From: "subha"<sip:subha172.16.10.124 >;tag=2c36ec2f
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 INVITE
> > > >
> > > > Allow: INVITE, ACK, CANCEL, OPTIONS,
BYE, REFER, NOTIFY, MESSAGE,
> > > > SUBSCRIBE, INFO
> > > >
> > > > Content-Type: application/sdp
> > > >
> > > > User-Agent: X-Lite release 1006e stamp
34025
> > > >
> > > > Content-Length: 236
> > > >
> > > > Message body
> > > >
> > > > Session Description Protocol
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Status-Line: SIP/2.0 100 Trying
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > > >
> > > > From: "subha"<
sip:subha172.16.10.124>;tag=2c36ec2f
> > > >
> > > > To: "ansuman"<
sip:ansuman172.16.10.124>
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 INVITE
> > > >
> > > > Server: Brekeke SIP Server rev.206
> > > >
> > > > Content-Length: 0
> > > >
> > > >
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Request-Line: INVITE sip:ansuman172.16.10.103:2072 SIP/2.0
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP
> > > >
172.16.10.124:5060;rport;branch=z9hG4bKea0b654b8805bbce.1
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > > >
> > > > Max-Forwards: 69
> > > >
> > > > Contact: <sip:subha172.16.10.124:5060>
> > > >
> > > > To: "ansuman"<
sip:ansuman172.16.10.124>
> > > >
> > > > From: "subha"<
sip:subha172.16.10.124>;tag=2c36ec2f
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 INVITE
> > > >
> > > > Allow: INVITE, ACK, CANCEL, OPTIONS,
BYE, REFER, NOTIFY, MESSAGE,
> > > > SUBSCRIBE, INFO
> > > >
> > > > User-Agent: X-Lite release 1006e stamp
34025
> > > >
> > > > Record-Route:
<sip:172.16.10.124:5060;lr>
> > > >
> > > > Content-Type: application/sdp
> > > >
> > > > Content-Length: 236
> > > >
> > > > Message body
> > > >
> > > > Session Description Protocol
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Status-Line: SIP/2.0 404 Not Found
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.124:5060
;rport=5060;branch=
> > > > z9hG4bKea0b654b8805bbce.1
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > > >
> > > > From: "subha" <
sip:subha172.16.10.124 >;tag=2c36ec2f
> > > >
> > > > To: "ansuman"
<sip:ansuman172.16.10.124>
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 INVITE
> > > >
> > > > Allow: INVITE, ACK, CANCEL, BYE, REFER,
OPTIONS, NOTIFY, SUBSCRIBE,
> > > > PRACK, MESSAGE, INFO
> > > >
> > > > Allow-Events: talk, hold, refer
> > > >
> > > > Supported: timer, 100rel, replaces,
callerid
> > > >
> > > > Content-Length: 0
> > > >
> > > >
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Status-Line: SIP/2.0 404 Not Found
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > > >
> > > > From: "subha" <
sip:subha172.16.10.124>;tag=2c36ec2f
> > > >
> > > > To: "ansuman"
<sip:ansuman172.16.10.124 >
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 INVITE
> > > >
> > > > Allow: INVITE, ACK, CANCEL, BYE, REFER,
OPTIONS, NOTIFY, SUBSCRIBE,
> > > > PRACK, MESSAGE, INFO
> > > >
> > > > Allow-Events: talk, hold, refer
> > > >
> > > > Supported: timer, 100rel, replaces,
callerid
> > > >
> > > > Content-Length: 0
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Request-Line: ACK sip:ansuman172.16.10.124 SIP/2.0
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport
> > > >
> > > > To: "ansuman" <
sip:ansuman172.16.10.124>
> > > >
> > > > From: "subha"<
sip:subha172.16.10.124>;tag=2c36ec2f
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 ACK
> > > >
> > > > Content-Length: 0
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Session Initiation Protocol
> > > >
> > > > Request-Line: ACK sip:ansuman172.16.10.103:2072 SIP/2.0
> > > >
> > > > Message Header
> > > >
> > > > Via: SIP/2.0/UDP
> > > > 172.16.10.124:5060;rport;branch=
z9hG4bKea0b654b8805bbce.1
> > > >
> > > > Via: SIP/2.0/UDP 172.16.10.102:23420
> > > >
;branch=z9hG4bK-d87543-5d10060a7926440d-1--d87543-;rport=234
20
> > > >
> > > > To: "ansuman" <
sip:ansuman172.16.10.124>
> > > >
> > > > From: "subha"<
sip:subha172.16.10.124>;tag=2c36ec2f
> > > >
> > > > Call-ID:
ZWU0MzY3YjIyN2NkYTUxYjE0NzY5OGY2ZGFiNDNjNTg.
> > > >
> > > > CSeq: 1 ACK
> > > >
> > > > Record-Route: <sip:
172.16.10.124:5060;lr>
> > > >
> > > > Content-Length: 0
> > > >
_______________________________________________
> > > > Sip-implementors mailing list
> > > > Sip-implementorscs.columbia.edu
> > > > https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
> > > >
> > > >
_______________________________________________
> > > > Sip-implementors mailing list
> > > > Sip-implementorscs.columbia.edu
> > > > https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
> > > >
> > > >
> > > >
____________________________________________________________
__________
> > > > This email has been scanned by the
MessageLabs Email Security
> > > > System.
> > > > For more information please visit http://www.messagela
bs.com/email
> > > >
> > > >
____________________________________________________________
__________
> > > >
> > > >
> > > >
> > > >
> > > >
------------------------------------------------------------
----------------------
> > > >
> > > > IMPORTANT The information contained in
this e-mail any
> > > > attachments is intended only for the
named recipient and may be
> > > > privileged or confidential.
> > > >
> > > > If you are not the intended recipient,
please notify us immediately
> > > > on +44 (0)1908 425000 and do not
disclose, copy, distribute
> > > > or take any action based on the contents
of this e-mail.
> > > >
> > > > You should understand and accept that,
when communicating with us
> > > > by e-mail, it is not a totally secure
communication medium.
> > > >
> > > > We accept no liability for any direct,
indirect or consequential
> > > > loss
> > > > arising from any action taken in
reliance on the information
> > > > contained
> > > > in this e-mail and give no warranty or
representation as to its
> > > > accuracy
> > > > or reliability.
> > > >
> > > > DIGITALK has the facility to monitor and
read both incoming
> > > > and outgoing communications by e-mail.
In line with industry
> > > > efforts
> > > > to reduce the proliferation of
Un-Solicited SPAM messages,
> > > > DIGITALK uses various methods including
Reverse-DNS
> > > > lookups and ban-lists to prevent
malicious content reaching our
> > > > users.
> > > >
> > > > This message and any attachments has
been scanned for known
> > > > viruses. However, we would advise you to
ensure the content is
> > > > indeed virus free. We do not, to the
extent permitted by law,
> > > > accept
> > > > any liability (whether in contract,
negligence or otherwise) for any
> > > > virus
> > > > infection and/or external compromise of
security and/or breach of
> > > > confidentiality in relation to
transmissions sent by e-mail.
> > > >
> > > > VAT No: GB 876 3287 81. Reg No: 3080801
> > > > Place of Registration: England
> > > > Registered Office Address: 2 Radian
Court, Knowlhill, Milton Keynes
> > > >
------------------------------------------------------------
----------------------"
> > > >
> > > >
> > > >
> > >
> > >
____________________________________________________________
__________
> > > This email has been scanned by the
MessageLabs Email Security System.
> > > For more information please visit http://www.messagela
bs.com/email
> > >
____________________________________________________________
__________
> > >
> > >
> >
> >
> >
____________________________________________________________
__________
> > This email has been scanned by the MessageLabs
Email Security System.
> > For more information please visit http://www.messagela
bs.com/email
> >
____________________________________________________________
__________
> >
>
>
_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
|