<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Aug 18, 2011 at 13:17, ik <span dir="ltr"><<a href="mailto:idokan@gmail.com">idokan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div><div></div><div class="h5">2011/8/18 Boris shtrasman <span dir="ltr"><<a href="mailto:borissh1983@gmail.com" target="_blank">borissh1983@gmail.com</a>></span><br></div></div><div class="gmail_quote">
<div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Hi , <br><br>with plain old SS7 we send a number and fill a field - how we got the calling number (Screening indicator), but what happen with SIP ?<br><br>I noticed a few practices how this data is passed (using a hint , P-Asserted-Identity and Remote-Party-ID ) but I'm searching for a common solution rather the checking all options to what should I expect when sending a SIP message from my SER to other networks (peering).<br>
<br>what would be a good solution for forwarding a blocked call ?<br>how should i fill the the invite on my ser so I could block / unblock call ?<br></div></blockquote></div></div><div><br>As far as I know, there is no single way of doing it. I do not know the whole RFC's of SIP, but in practice it depends on the provider gateway. <br>
</div></div></div></blockquote><div><br>So a good practice is to use all the known options ?</div><br></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div></div>