<DIV>Yes, Ben you are right. </DIV>
<DIV>Asterisk is a B2BUA. When the call passes through the ingress and egress sip call ids are different. By using $SIPCALLID I can easily get the sip call id that User A sends. The question is how to "accessing SIP callid of the INVITE sent to User B"? By senting Manager interface channel query commands I can get the egress sip call id but it is not that easy. Just want to know if there is any a simple way to do that.</DIV>
<DIV> </DIV>
<DIV>Thanks a lot.</DIV>
<DIV> </DIV>
<DIV>Ray</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello Steve,<BR>I think Ray was talking more like the following setup (do correct me if<BR>I am wrong):<BR><BR>User A (SIPcallId1) ---> Asterisk (SIPcallId2) ------> User B<BR><BR>In this case, the INVITE SIP callId received by Asterisk from User A is<BR>different to that sent in the INVITE to User B.<BR>I can get User A's callId using ${SIPCALLID}. How about accessing SIP<BR>callid of the INVITE sent to User B??<BR>Typical need for this, is to store both the callIds to store in the CDRs<BR>for debugging purposes(w.r.t. the service provider, et al).<BR><BR>cheerz<BR>- Ben.<BR><BR>Steve Totaro wrote:<BR><BR>> You can capture the sipcallid from the manager output. The cool <BR>> part is that the sipcallid is the same on both sides of a call. <BR>> So, AsteriskA--->SIP (sipcallid)----> AsteriskB SIP (Same sipcallid <BR>> as AsteriskA for that call.<BR>><BR>> It is really easy to capture it from the manager.<BR>><BR>> Thanks,<BR>> Steve<BR><?xml:namespace prefix = sip /><sip:2519494@10.10.10.67><sip:12124441782@10.10.10.107><sip:2519494@10.10.10.67><sip:12345678@10.10.10.100:11060></BLOCKQUOTE></sip:12345678@10.10.10.100:11060></sip:2519494@10.10.10.67></sip:12124441782@10.10.10.107></sip:2519494@10.10.10.67><BR>
--
<div> Want an e-mail address like mine? </b><br>
Get a <b>free e-mail </b>account today at <a href="http://www.mail.com/Product.aspx" target="_blank">www.mail.com</a>!</div>