Hi Experts
Normally, In case of SIP signaling, hold and retrieve indication is
carried in the signaling messages, in the SDP carried by the SIP INVITE
or UPDATE messages .
Can i have some detailed description about the attributes part i.e
a=sendrecv , inactive ,recvonly ,etc...
Thanks,
Normally, In case of SIP signaling, hold and retrieve
indication is carried in the signaling messages, in the
SDP carried by the SIP INVITE or UPDATE messages .
Can i have some detailed description about the attributes
part i.e a=sendrecv , inactive ,recvonly ,etc...
See the
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Brez
Borland
Thank you for input everybody! I am curious, what about Java and C#, do
they
have libraries to resolve NAPTR?
Speaking for C# I
Hi,
Just adding some information, RFC3261 allows sending re-invite without SDP
body. I don't think this is a good idea because the UA witch sends a re-invite
with a new renegotiation should present its alternatives. I remmember that RFC
says 'MAY', witch preciselly means it's possible but it's
RFC 3261 section 3 indicates to use RFC 2119's interpretation of MAY.
5. MAY This word, or the adjective OPTIONAL, mean that an item is
truly optional. One vendor may choose to include the item because a
particular marketplace requires it or because the vendor feels that
it enhances
ACM IPTComm 2011 - Call for Participation
=
Dear Colleague,
we invite you to participate in the ACM IPTComm 2011. The conference is
held on August 1-2, 2011 at the Illinois Institute of Technology
Chicago, Illinois, USA.
The deadline for early
Hi Experts ,
What is the basic/Main difference between SIP-I , SIP-T normal SIP .
Thanks,
Best Regards
sAlil veRmA
Tech . Supp. Grp ( Care Team )
NCS : sip: salil.ve...@nsn.com mailto:salil.ve...@nsn.com
___
Sip-implementors mailing list
Hello,
A) SIP-I have the body SDP and plus the body ISUP. ( IAM--- trunk- TDM
--- MGC invite/sdp/iam -- MGC --- TDM --- trunk --- IAM ( I am
here again))
INVITE/SDP/IAM
SIP-T For ISUP-SIP Interconnections or SIP-I are similar :
SIP-I and SIP-T refer to two very similar approaches
From: Johnson, Michael A [michael.a.john...@team.telstra.com]
The PBX (Mitel) that sends the re-invite without SDP, that then
accepts the offered G.729 codec from the ISP, despite not being able
support the codec is the device I believe is as fault. The
manufacturer however disagrees.
On 07/01/2011 02:24 PM, Worley, Dale R (Dale) wrote:
From: Johnson, Michael A [michael.a.john...@team.telstra.com]
The PBX (Mitel) that sends the re-invite without SDP, that then
accepts the offered G.729 codec from the ISP, despite not being able
support the codec is the device I believe is
On 7/1/2011 5:12 PM, Kevin P. Fleming wrote:
On 07/01/2011 02:24 PM, Worley, Dale R (Dale) wrote:
From: Johnson, Michael A [michael.a.john...@team.telstra.com]
The PBX (Mitel) that sends the re-invite without SDP, that then
accepts the offered G.729 codec from the ISP, despite not being
SIP-I was developed by the ITU in 2004, and made use of most of the
constructs defined in the IETF SIP-T effort. It is defined by ITU-T
Q.1912.5.
Also, ANSI SIP-I is defined in T1.679
--
Regards
Harsha
___
Sip-implementors mailing list
12 matches
Mail list logo
