Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: domainwizard on May 24, 2008, 05:55:58 AM

Title: to be RFC3261 or not to be RFC2543 ?
Post by: domainwizard on May 24, 2008, 05:55:58 AM

kinda has a hamlet ring to it...

don't have a clue ...oh which to use?
and what the heck is RFC encoding and do i need it?

heh

Title: Re: to be RFC3261 or not to be RFC2543 ?
Post by: SARK devs on May 24, 2008, 09:36:01 AM

Er... hmmmm

Quote

rfc2543, "SIP: Session Initiation Protocol," that was obsoleted by rfc3261, "SIP: Session Initiation Protocol" 
that was published as rfc2543, "SIP: Session Initiation Protocol" 

3261 and 2543 are not encoding standards but SIP itself.

Perhaps you are referring to RFC 2833 (RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals)? As the title suggests, RFC2833 describes how to transmit DTMF and call-signalling information in an RTP packet, as opposed to transmitting it out-of-band  (in the SIP header, usually referred to as info or sip-info), or transmitting it in-band as an undifferentiated part of the overall audio signal.  The only thing you really need to know about this stuff is that both sender and receiver should be setup to use the same method and that you can't use in-band with a compressive codec (i.e. with anything other than G711 law).

Kind Regards

S
 

Title: Re: to be RFC3261 or not to be RFC2543 ?
Post by: domainwizard on May 25, 2008, 04:04:41 AM

the question was inspired by a Chinese phone called ip0027, it gives a choice between the two sip standards that of course is not well documented, the issue is that the fones from time to time show up as unregistered, yet one can still telnet to them. i  was perplexed which standard was the better choice.
i think the issue was resolved by checkin some boxes and unchecking others until the darn things worked. the documentation that came with them was written in chinglish which might follow the ya get what ya pay for rule... i can certainly see the value in name brand hardware for future needs.

many regards
 

Title: Re: to be RFC3261 or not to be RFC2543 ?
Post by: SARK devs on May 25, 2008, 11:36:48 AM

Ah, -  good old Tiger Net.  There isn't a month goes by when they aren't trying to offload a container of phones to us. :-)


Still, you can't blame 'em for trying.

Best

S

Title: Re: to be RFC3261 or not to be RFC2543 ?
Post by: domainwizard on May 27, 2008, 02:50:37 AM

itwould seem for sark rfc2543 is the correct answer as they have remained happily connected for 24 hrs without falling off, subsequent to the change..

hail to the gods of trial and error :-p who watch over the ip0027 fones

cheers  :pint: