The closest thing I can think of is S/MIME signatures and certificates that of
course are encoded in text, but is not text in the data.
There are actually references to sending images in RFC 3261:
"The disposition type icon indicates that the body part contains an image
suitable as an iconic rep
rfc 3204 seems to define binary encoding for ISUP and QSIG signaling bodies.
Thanks
Rajesh Jain
On Tue, Nov 1, 2011 at 9:33 AM, Iñaki Baz Castillo wrote:
> 2011/10/31 Kevin P. Fleming :
> > Any MIME-type that is defined to have binary content could legitimately
> > appear in a SIP message. I'm
2011/10/31 Kevin P. Fleming :
> Any MIME-type that is defined to have binary content could legitimately
> appear in a SIP message. I'm not personally aware of any RFCs that
> define SIP extensions that require the transport of binary message
> bodies, but it's certainly allowed. RFC 3261 places no
On 10/31/2011 03:20 PM, Iñaki Baz Castillo wrote:
> 2011/10/31 Worley, Dale R (Dale):
>>> From: Iñaki Baz Castillo [i...@aliax.net]
>>>
>>> Hi, is there any RFC defining a binary body for SIP (in contrast to
>>> UTF-8/ASCII bodies)?
>>
>> RFC 3261 section 7.4.1:
>>
>>SIP messages MAY contain bi
2011/10/31 Worley, Dale R (Dale) :
>> From: Iñaki Baz Castillo [i...@aliax.net]
>>
>> Hi, is there any RFC defining a binary body for SIP (in contrast to
>> UTF-8/ASCII bodies)?
>
> RFC 3261 section 7.4.1:
>
> SIP messages MAY contain binary bodies or body parts. When no
> explicit charset para
> From: Peter Krebs [pkr...@gmail.com]
>
> I noticed, to my horror, that the SIP grammar actually allows ASCII NULL
> characters in certain message elements (Reason-Phrase, quoted string,...are
> there any more?). Is there any actual sense in using this characters in said
> elements other than giv
> From: Iñaki Baz Castillo [i...@aliax.net]
>
> Hi, is there any RFC defining a binary body for SIP (in contrast to
> UTF-8/ASCII bodies)?
RFC 3261 section 7.4.1:
SIP messages MAY contain binary bodies or body parts. When no
explicit charset parameter is provided by the sender, media subty
+1
On 10/31/11 10:46 AM, Worley, Dale R (Dale) wrote:
>> From: Olle E. Johansson [o...@edvina.net]
>>
>> RFC 3261 is not totally clear in the topic of AORs you can register
>> to. It seems to indicate any URI, but mentions usernames in most
>> examples.
>
> In practice, what you can register to is
> From: Verma, Salil (NSN - IN/Gurgaon) [salil.ve...@nsn.com]
>
> Is SIP CONNECTIVITY supportMULTIHOMING . ? If so what are the requirments .
>
> Actually when one router goes down than sip connectivity is also down
> so we want to know can we create multihoming on SIP connect .
The commonest te
2011/10/31 Pavesi, Valdemar (NSN - US/Irving) :
> It will be registered by contact header not by to-header
Oh please You register for receiving requests sent to the URI in
the "To" header of the REGISTER. And you will receive them in the
Contact URI of the REGISTER.
This changes *nothing*.. O
31 okt 2011 kl. 15:46 skrev Worley, Dale R (Dale):
>> From: Olle E. Johansson [o...@edvina.net]
>>
>> RFC 3261 is not totally clear in the topic of AORs you can register
>> to. It seems to indicate any URI, but mentions usernames in most
>> examples.
>
> In practice, what you can register to is
> From: Olle E. Johansson [o...@edvina.net]
>
> RFC 3261 is not totally clear in the topic of AORs you can register
> to. It seems to indicate any URI, but mentions usernames in most
> examples.
In practice, what you can register to is what the registrar for the
domain in question will accept. S
It will be registered by contact header not by to-header
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext
Olle E. Johansson
Sent: Monday, October 31, 2011 7:20 AM
To:
sip-implement...@lists.cs.
2011/10/31 Olle E. Johansson :
> So can I REGISTER with a "To: sip:sales.edvina.net" ?
IMHO the spec allows it.
--
Iñaki Baz Castillo
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/lis
RFC 3261 is not totally clear in the topic of AORs you can register to. It
seems to indicate any URI, but mentions usernames in most examples. The
definition of address-of-record is
" Address-of-Record: An address-of-record (AOR) is a SIP or SIPS URI
that points to a domain with a loc
Hi Experts ,
Query :-
Is SIP CONNECTIVITY supportMULTIHOMING . ? If so what are the requirments .
Summary :-
Actually when one router goes down than sip connectivity is also down so we
want to know can we create multihoming on SIP connect .
Thanks,
Best Regards
sAlil veRmA
Customer S
16 matches
Mail list logo
