Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SIP V2 ??
- Thread starter george74
- Start date
hairlessupportmonkey
IS-IT--Management
Since SIP isnt really a standard as such, then its difficult to say, since may providers all have different says of presenting it.....
try it and find out!
try it and find out!
UGGGG... :-( Questions like this just make me realize that the marketing retards have really won the minds of some.
What is SIP v2 really? The first officially released version of the SIP RFC was 2543. This was refined to the more modern RFC 3261 so is this SIP v2? If there is no RFC to define it then it doesn't exist and is nothing more than marketing fluff. So what defines "SIP v2"?
IP Office supports the following RFCs. Take a look at any "SIP v2" device and find out what RFCs they support and compare then see if any that they might support that we do not are important to your application.
RFC 3261 - SIP session Initiation Protocol
RFC 1889 – RTP
RFC 1890 - RTP Audio
RFC 4566 – SDP
RFC 2833 - RTP /DTMF
RFC 3264 - SDP Negotiation
RFC 3265 - Event Notification
RFC 3515 - SIP Refer
RFC 3842 - Message Waiting
RFC 3310 – Authentication
RFC 2976 – INFO
RFC 3323 - Privacy for SIP (PAI) and draft-ietf-sip-privacy-04 (RPID)
Kyle Holladay
ACSS SME Communications
ACE Implement: IP Office
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA
"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
What is SIP v2 really? The first officially released version of the SIP RFC was 2543. This was refined to the more modern RFC 3261 so is this SIP v2? If there is no RFC to define it then it doesn't exist and is nothing more than marketing fluff. So what defines "SIP v2"?
IP Office supports the following RFCs. Take a look at any "SIP v2" device and find out what RFCs they support and compare then see if any that they might support that we do not are important to your application.
RFC 3261 - SIP session Initiation Protocol
RFC 1889 – RTP
RFC 1890 - RTP Audio
RFC 4566 – SDP
RFC 2833 - RTP /DTMF
RFC 3264 - SDP Negotiation
RFC 3265 - Event Notification
RFC 3515 - SIP Refer
RFC 3842 - Message Waiting
RFC 3310 – Authentication
RFC 2976 – INFO
RFC 3323 - Privacy for SIP (PAI) and draft-ietf-sip-privacy-04 (RPID)
Kyle Holladay
ACSS SME Communications
ACE Implement: IP Office
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA
"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
- Thread starter
- #4
My point is however that even a bundle of some RFCs would have to be defined to be considered a standard. I've seen devices tout SIP v2 with RFC 3261, 3262, 3263 and 3264.
3261 is obvious, you can't have SIP without SIP
3262 PRACK isn't supported
3263 Locating isn't supported although we can resolve via DNS
3264 Offer/Answer isn't supported. Although in that we only "support" those "supported" devices we don't have much need to reject unsupported services in SDP.
I see the part of the goal here. Plug in any device and let everything work itself out. Never really been an Avaya mindset. They tend to be of the opinion that you plug in those devices that we tell you will work in the way we say they will work and things should go as planned.
Kyle Holladay
ACSS SME Communications
ACE Implement: IP Office
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA
"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
3261 is obvious, you can't have SIP without SIP
3262 PRACK isn't supported
3263 Locating isn't supported although we can resolve via DNS
3264 Offer/Answer isn't supported. Although in that we only "support" those "supported" devices we don't have much need to reject unsupported services in SDP.
I see the part of the goal here. Plug in any device and let everything work itself out. Never really been an Avaya mindset. They tend to be of the opinion that you plug in those devices that we tell you will work in the way we say they will work and things should go as planned.
Kyle Holladay
ACSS SME Communications
ACE Implement: IP Office
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA
"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
- Status
