From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <[EMAIL PROTECTED]>
>Personally I don't understant why "486 User Busy" is used for
>rejecting a call.
>
> One reason is to reject the call without returning to the caller an
> explicit indication that the call has been rejected
From: Paul Kyzivat <[EMAIL PROTECTED]>
Its worse than that. The GW may have opened up a pstn connection based
on the partial number, and received info back which results in the 484.
The retry with more digits needs to reach the gw that still has that state.
And this query into the P
Response below,
Cheers,
Lincoln
Brett Tate wrote:
>> Can anyone please let me know is there any
>> scenario wherein it will be required that
>> Subscriber makes a call to himself?
>>
>
> The common example is users dialing there own number as a mechanism to
> connect to their voice mail se
> Can anyone please let me know is there any
> scenario wherein it will be required that
> Subscriber makes a call to himself?
The common example is users dialing there own number as a mechanism to
connect to their voice mail server; however I'm not sure if actually
discussed within the IMS docu
One of the scenarios where "it certainly can be useful for X1 to call
X2" is where you want to move select media streams in a call or an whole
established call between two entities (devices) using "AOR X"
--
Srini Krishnamoorthy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAI
> >
> > So it doesn't seem that you will ever need to expend additional
effort
> > to get 484s to work correctly.
>
> Its worse than that. The GW may have opened up a pstn connection based
> on the partial number, and received info back which results in the
484.
> The retry with more digits need
I agree with you that the definitions of the codes are not entirely
clear. IMO 404 is not an appropriate response for a known and supported
AOR for which no device is currently registered.
Paul
Iñaki Baz Castillo wrote:
> El Tuesday 04 March 2008 19:07:14 Paul Kyzivat escribió:
>> A UAS
If phones X1 and X2 are both registered with AOR X it certainly can be
useful for X1 to call X.
There is nothing about sip signaling that should in any way prevent this
from working.
It is of course possible in such a case for a UAC to receive an INVITE
from itself. In most situations it would
Dale,
at end...
[EMAIL PROTECTED] wrote:
>From: "Attila Sipos" <[EMAIL PROTECTED]>
>
>> What if you are using something like DNS SRV to route to a
>> group of gateways? How can one ensure all new requests go the
>> same gateway?
>>
>>Why would you want to?
>
>
[EMAIL PROTECTED] wrote:
> Thanks paul!
> Now what I am concerned with is: why in this case, the 180 Ringing is
> not permitted to carry SDP? Based on what kind of consideration? Thanks!
Because it doesn't follow any of the specified patterns for conveying
offers and answers. Look at
http://w
You can do that, there is no restriction on that.
On Tue, Mar 4, 2008 at 11:39 PM, Sumin Seo <[EMAIL PROTECTED]> wrote:
> Thanks Harsha.
>
> My first question is about the purpose of Warning header.
> Can I user this Warning header only for specifying SDP related
> information?
>
> Instead of Rea
this is a good question.
Since no one has answered I'll try...
I think they are a bit like regular expressions.
[] usually means an optional component
<> can be a tag which can be substituted for some value.
In HTML or XML, it marks the start or end of some element.
* usually means zero or m
Get that information from the 8.2.6.2 Headers and Tags paragraph.
Regards,
Srinivas CH,
Huawei Technologis India Pvt Ltd,
1st Floor 'A' Tower,Diamond District,
Airport Road, Bangalore-8,
Contact: (Off) 080-41117676 ext: 3220(Mob) +919448865786.
This e-mail and attachments co
El Wednesday 05 March 2008 10:42:28 Andreas Byström escribió:
> Does "user not registered" really fit into the description of 404 in
> RFC3261? A subscriber that isnt registered does still exists in the domain
> that is handled by the server, doesnt it? I would say that the description
> of 480 is
El Wednesday 05 March 2008 10:05:16 Iñaki Baz Castillo escribió:
> El Tuesday 04 March 2008 19:07:14 Paul Kyzivat escribió:
> > A UAS should not in general know whether it has been called by a gateway
> > or some other sip device. And so it should not be adjusting its
> > responses based on the kin
Does "user not registered" really fit into the description of 404 in RFC3261? A
subscriber that isnt registered does still exists in the domain that is handled
by the server, doesnt it? I would say that the description of 480 is better for
the unregistered case. RFC3261:
El Wednesday 05 March 2008 10:19:22 srinivas escribió:
> Hi,
> The UAS may generate the To-Tag in 100 responses according to
> RGFC3261
> If a request contained a To tag in the request, the To header field
> in the response MUST equal that of the request. However, if the To
> h
Hi, Philips iS3000 SIP Server (a PBX) creates a "To_tag" in the "100 Trying".
Is it valid?
Thanks a lot.
--
Iñaki Baz Castillo
[EMAIL PROTECTED]
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cu
El Wednesday 05 March 2008 05:29:25 [EMAIL PROTECTED] escribió:
>Personally I don't understant why "486 User Busy" is used for
>rejecting a call.
>
> One reason is to reject the call without returning to the caller an
> explicit indication that the call has been rejected by the callee.
Be
El Tuesday 04 March 2008 19:07:14 Paul Kyzivat escribió:
> A UAS should not in general know whether it has been called by a gateway
> or some other sip device. And so it should not be adjusting its
> responses based on the kind of thing it thinks is calling.
>
> The response returned by the UAS sho
20 matches
Mail list logo
