Cell Relay Archive

[Alex Hardisty <alex@pqm-cons.demon.co.uk>]

In article <33E11E64@msgate.future.futsoft.com>, sripriyar
<sripriyar@future.futsoft.com> writes

>>    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.

Alex Hardisty
PQM Consultants, Suite C, 17 Moor Street, Chepstow, NP6 5DB, UK
tel: +44 1291 626 180 / fax: +44 1291 626 190
email: alex@pqm-cons.demon.co.uk www: http://www.pqm-cons.demon.co.uk/