Hi Sushil,
It is not a SIP method.
The draft "http://www.ietf.org/internet-drafts/
draft-burger-sipping-netann-07.txt"
defines 'Basic Network Media Services with SIP' which includes netannc
(network announcements).
Elias
Hughes Software Systems
http://www.hssworld.com
"Sushil Kumar
Verma"
<[EMAIL PROTECTED] To
l.com> <[EMAIL PROTECTED]>
Sent by: cc
sip-implementors-
[EMAIL PROTECTED] Subject
ia.edu [Sip-implementors] SIP NETANNC
method
01/22/04 11:43 AM
Hi,
Is there any SIP method called NETANNC?
If yes kindly inform me where I can get the info on that.
Thanks in advance.
rgds,
Sushil
-------Original Message-------
From: [EMAIL PROTECTED]
Date: Wednesday, January 21, 2004 10:33:44 PM
To: [EMAIL PROTECTED]
Subject: Sip-implementors Digest, Vol 10, Issue 15
Send Sip-implementors mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sip-implementors digest..."
Today's Topics:
1. Experience with Windows Messenger 5.x SIP support (Arlie Davis)
2. How many NAPTR records are allowed/required? (Franz Edler)
3. SIPIT 14 late registration (Robert Sparks)
----------------------------------------------------------------------
Message: 1
Date: Tue, 20 Jan 2004 16:14:08 -0500
From: "Arlie Davis" <[EMAIL PROTECTED]>
Subject: [Sip-implementors] Experience with Windows Messenger 5.x SIP
support
To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I'm trying to get Windows Messenger 5.x to work with several different
SIP proxies/registrars, including one I am developing. I've had some
success and some failure.
Has anyone been able to get Messenger 5.x to work with any known SIP
proxy/registrar? (It's using the MS RTC SIP stack.) I'm able to get
Messenger to register, and even presence information works correctly.
However, if I try to use Messenger to send and receive instant messages,
it fails. The net capture looks like this:
A = Windows Messenger 5.x client
B = Windows Messenger 5.x client
R = SIP proxy / registrar
A -> R: REGISTER
R -> A: 200 OK
B -> R: REGISTER
R -> B: 200 OK
[leaving out SUBSCRIBE/NOTIFY]
On A, open IM window for user at B. Type something, hit enter.
A -> R: INVITE
R -> B: INVITE
B -> R: 100 Trying
B -> R: 200 OK
R -> A: 100 Trying
R -> B: 200 OK
B -> A: BYE
A -> B: ACK [race condition]
B -> A: 481 No call leg/transaction
Looking at the network capture, and at the trace information emitted by
MS RTC stack, apparently B receives the INVITE, accepts it, then
immediately terminates the session. Any ideas why?
Any help is appreciated.
-- arlie
------------------------------
Message: 2
Date: Wed, 21 Jan 2004 14:28:25 +0100
From: "Franz Edler" <[EMAIL PROTECTED]>
Subject: [Sip-implementors] How many NAPTR records are
allowed/required?
To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I am a little bit confused about the following statement in RFC 3263
chapter
4.1:
If a SIP proxy, redirect server, or registrar is to be contacted
through the lookup of NAPTR records, there MUST be at least three
records - one with a "SIP+D2T" service field, one with a "SIP+D2U"
service field, and one with a "SIPS+D2T" service field.
Some paragraphs before I can read:
If the server supports multiple transport protocols, there will be
multiple NAPTR records, each with a different service value.
I understand, that three NAPTR records are the maximum for a given server,
if it supports all three transport services. But that does not fit to the
above mentioned clause stating "there MUST be at least three records...".
Can anyone help me to understand this?
FRanz
------------------------------
Message: 3
Date: Wed, 21 Jan 2004 09:52:28 -0600
From: Robert Sparks <[EMAIL PROTECTED]>
Subject: [Sip-implementors] SIPIT 14 late registration
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain
As there have been several requests to register for SIPIT 14 after
last Friday's registration deadline, ETSI has graciously extended
registration to this Friday (23 Jan).
RjS
------------------------------
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
End of Sip-implementors Digest, Vol 10, Issue 15
************************************************
____________________________________________________
IncrediMail - Email has finally evolved - Click Here
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
