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
ul Kyzivat
Sent: 05 March 2008 13:46
To: [EMAIL PROTECTED]
Cc: Sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] "484 Address Incomplete" - overlap
dialling- ensuring all messages go to same PSTN gateway (RFC3578)
Dale,
at end...
[EMAIL PROTECTED] wrote:
>From:
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?
>
>
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?
Maybe I wasn't clear.
I want all the overlapped dialling
TECTED] on behalf of [EMAIL PROTECTED]
Sent: Mon 03/03/2008 20:58
To: Sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] "484 Address Incomplete" - overlap dialling-
ensuring all messages go to same PSTN gateway (RFC3578)
From: "Attila Sipos" <[EMAIL
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?
Dale
___
Sip-implementors mailing list
Sip
484 seems to me, a very bad way of doing overlapped dialling in SIP.
rfc 3578 (http://www.ietf.org/rfc/rfc3578.txt) says:
Routing in SIP can be controlled by the administrator of the network.
Therefore, a gateway can be configured to generate SIP overlap
signalling in
