[STDS-802-16] Application level signaling ..
- To: STDS-802-16@LISTSERV.IEEE.ORG
- Subject: [STDS-802-16] Application level signaling ..
- From: Rakesh Avichal Ughreja <rakesh.ughreja@gmail.com>
- Date: Wed, 2 Feb 2005 12:35:34 +0530
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=joUMQi6D2WXKvieHCyEfLYYVnf92nsyFlt9hbJlS9tIsJtxzUYiHy1V+1oHZHU5fbwLOWc19QKTlUw79h1Jwm6j9fhy10wXTBJlZ8OdIrLjqUiLbjQr8MPV0z2RaJlIM8FYPkIhHNtbACKcvzUGRPds3X8R8HZwJO4h5wLPe+JY=
- Reply-To: Rakesh Avichal Ughreja <rakesh.ughreja@gmail.com>
- Sender: owner-stds-802-16@LISTSERV.IEEE.ORG
Hi,
Which CID will be used for sending the upper layer singling messages
like SIP, is it going to be on Secondary management CID ?
In my understanding the SIP signaling messages should be considered as
a BE traffic, and it should have new CID(excluding Basic, Primary and
Secondary). This CID is valid till the SIP transaction(not the
session) is alive. CID should be destroyed once the transaction is
over.
Please ignore this if this is not the correct forum to ask this
question. In that case I would be happy if you can redirect me to
proper place to ask this question.
--
Regards,
Rakesh
Success consists of going from failure to failure without loss of enthusiasm.
~ Winston Churchill ~