Cell Relay Archive

["naveen rajanikantha" <rnavina@hotmail.com>]

 I think that the network allocates the CONNECTIONID, so the SETUP 
message from NETWORK to USER will always(I think it is mandatory) 
contain the CONNECTIONID. So if the USER cannot accept this CONNECTIONID 
it should reject the call at this stage itself. 

    If the CONNECTIONID sent by the USER in CALLPROCEEDING is 
inconsistent with the earlier CONNECTID in the SETUP message, the 
NETWORK should REJECT the call. 

    The Network should check for the CONNECTID in the CONNECT message 
from the USER, if it is inconsistent with the CONNECTID in SETUP, the 
call will be cleared by the Network.

Hope this helps,

Naveen R
rnavina@hotmail.com






----------------------------------------------------------------------------  
> --
>Alex Hardisty wrote:
>
>>>>    How to process different connectID of callproceeding message and
>>>>connect message from  user to network?
>>>>when network send SETUP to user,user responses with CALLPROCEEDING
>>>>filling with connectID1 IE,after that,user send CONNECT filling with
>>>>connectID2 IE to network,but,connectID1 is not consistent with
>>>>connectID2,how can network do ? ignore/release?
>
>>>The network should release the call. From the specs it is clear that, 
the
>>>network may accept the connection identifier (if it is available)  
sent 
>only
>>>in the first response message to SETUP by the user. So network will 
not
>>>consider the connection identifer received in the second message.
>>>Even if we take the case where network accepts the connection 
identifier
>>>from the second message, there is no way of network informing the 
user 
>which
>>>connection identifier it has accepted (whether the one received in 
the 
>call
>>>proceeding or in the connect).
>
>>No. Since the Connection identifier information element has already 
been
>>received in the first response to SETUP (i.e., the CALL PROCEEDING), 
if
>>it is subsequently received in another message it should be treated as 
a
>>non-mandatory information element content error (subclause 5.5.6.8.2 
of
>>UNI 3.1). The call should not be released.
>
>The actual question posted in this list is not about receiving the same 
>connection identifier in subsequent messages (apart from the first 
response 
>to SETUP), but about receiving a different connection identifier. If 
the 
>same connection identifier (non-mandatory IE in this case) is present 
in 
>CONNECT message also, then no problem. Though specification doesn't 
mention 
>anything regarding this case, it is logical enough to release the call 
as 
>the user would not know which connection identifier to use.
>
>
>Regards,
>Sripriya R.
>sripriyar@future.futsoft.com
>Future Software Private Limited,
>Madras, India.
>
>
>


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com