Girish,
There are no rules here. IETF only standardizes the protocol, not the
construction of stacts that support it. You are free to construct the
stack any way you, and the users of your stack, desire.
Paul
Girish Moodalbail wrote:
> Thanks Robert for the response.
>
> From your re
Thanks Robert for the response.
From your reply I understood that within a dialog if a re-INVITE is
issued than
the dialog layer in the SIP Stack should not populate the Contact header
of the
re-INVITE request. It's left to the application to add the same Contact
header (if
it has not changed
Both are used.
Typically stacks layer what they offer - they have a transaction
layer that doesn't know about dialogs
and a higher layer that abstracts dialogs into things like calls or
subscriptions. The first thing would
not autopopulate the local target (in the contact). The second
typica
Hello all,
I have this question on creating a request within the dialog. As per the
RFC 3261, Section 12.2.1.1
"Generating the Request", that UAC should add the contact header.
"
A UAC SHOULD include a Contact header field in any target refresh
requests within a dialog, and unless there is
From: "Santosh Yadawad" <[EMAIL PROTECTED]>
When UA sends INVITE message it will query the NAT and will
get the public ip-address from its private ip-address.
So what will be the contact header field in INVITE Message
weather its public ip (obtained from NAT) or it's a private (lo
Thanks to all who responded!
I find P-Asserted-Identity to be the best solution and here is why.
1. Because of its simplicity it is very likely already supported by major
telecom companies.
2. What Michael suggested may be used but has serious limitations as pointed
out by Chandra. In addition,
The event is currently planned for the week of November 5 in Beijing.
We're still finalizing things with the host, so the details could
change.
Watch www.sipit.net for the official announcement and the start of
registration.
RjS
On Jul 12, 2007, at 2:08 AM, Richard wrote:
>
> Dear all,
> S
Hi Michael,
Great response ..i understood but I want to say another scenario...
If A calls B(where A and B are in different networks) and assume that B
had enabled FMFM(finf me follow me) feature to C,D,E it means if B is
not available then call be forwarded to C,D and E.Now finally when E
gets
Your description is basically right, but your conclusion is wrong! I'll
try to explain a little more clearly.
Assume a dialog (D1) between A and B, and that A wishes to change the
name that B is displaying. To do this, A sends a new INVITE, creating a
new dialog (D2). This new INVITE contains
Hi,
"Replaces" header field is to replace an existing dialog..
Assume that session is established between A and B then A want to
change the dialog ..then A has to send reINVITE request with "replaces "
header field ..then if B accepts that reinvite then..for exisiting
dialog it has to send
In addition to Jerry's two suggestions, another popular technique is to
send an INVITE with Replaces header instead of the reINVITE. You can
update all manner of indications in the new initial INVITE, which most
phones will use to update their display.
See RFC 3891 for details of the replaces hea
Dear all,
Sorry to post this message in this newsgroup. I would like to when is
the next SIPIT event. Actually we have joined 15th and 17th SIPIT event.
Thank you very much.
Regards
Richard WU
Senior Engineer
Consumer Electronics
ASTRI
This message (including any attachments) is for the named
12 matches
Mail list logo
