<div dir="ltr">Hi,<div> INFO is generated in early stage. </div><div><br></div><div>The information I provided in my original post was not entirely accurate. My setup was as follows:</div><div><br></div><div>Carrier PRI ----- Siemens PBX (4000) ---(tried qsiq and primary-ni) --- Cisco 3845 ---- PROXY</div><div><br></div><div>After more debugging we found out that Siemens was not passing the correct information in the ISDN setup messages. Specifically, it was missing the following:</div><div><br></div><div><div style="font-size:14px;font-family:Calibri,sans-serif"><font color="#ff0000">"Operation = InformationFollowing (calling_name)</font></div><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#ff0000"> Name information in subsequent FACILITY message” </font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#ff0000"><br></font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000">We then connected the carrier PRI directly into the media gateway and that resolved the issue. Cisco gateway was already configured to act similar to how Jeff described the Adtran configuration. We started seeing the correct calling name as soon as the PRI was connected directly.</font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000"><br></font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000">Thank you for the followup.</font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000"><br></font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000">Best regards,</font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000"><br></font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000">--</font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000">Zahid</font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000"><br></font></pre><pre style="white-space:pre-wrap;font-size:14px;font-family:Calibri,sans-serif;margin:0em"><font color="#000000"><br></font></pre></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 6, 2016 at 4:49 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<tt>Hi Zahid,<br>
<br>
When in the dialog is the INFO injected ? in the early stage ? or
after the call is established ? <br>
<br>
Best regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre><div><div class="h5">
<div>On 18.12.2015 17:12, Zahid Mehmood
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Jeff,
<div> Thanks for your response. >From what I understand
from Cisco documentation, gateway seems to act that way when
using H323 but, sadly, not for SIP. I will push Cisco about
this.</div>
<div><br>
</div>
<div>Assuming the worst, Is there any thing I can try on the
proxy side to get the desired results?</div>
<div><br>
</div>
<div>Regards,</div>
<div>--</div>
<div>Zahid</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Dec 18, 2015 at 9:44 AM, Jeff
Pyle <span dir="ltr"><<a href="mailto:jeff.pyle@fidelityvoice.com" target="_blank">jeff.pyle@fidelityvoice.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">In Adtran TA900 series gateways (very
Cisco-like) I'm able to configure the PRI interface to
wait for the FACILITY message before sending the initial
INVITE. When the INVITE does leave the gateway towards
the proxy, it has full caller name information. Perhaps
something like this is available on the Cisco. I hope so,
because if not, you're going to have a difficult time
integrating the INFO message.
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Thu, Dec 17, 2015 at 2:53 PM,
Zahid Mehmood <span dir="ltr"><<a href="mailto:zm23@columbia.edu" target="_blank"></a><a href="mailto:zm23@columbia.edu" target="_blank">zm23@columbia.edu</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">Hi,
<div> I am having trouble figuring out how
to process the calling-name coming from the
PRI. In my setup, PRI is connected to a
Cisco media gateway which sends traffic to
the proxy servers. Calling name is not
coming in the ISDN setup message. It is
actually provided in a separate facility
message [1].</div>
<div><br>
</div>
<div>Cisco gateway processes this secondary
messages and generates a INFO message.
Polycom phone sends the 200 ok message but
there is no change in the visible caller id.</div>
<div><br>
</div>
<div>
<div>Does anyone have a working example or
suggestion of how this is supposed to
work? </div>
</div>
<div><br>
</div>
<div>Invite:</div>
<div><br>
</div>
<div>
<div>U 2015/12/17 14:20:31.215540
<!-- <a href="http://10.10.1.1:50975" target="_blank"> -->10.10.1.1:50975<!-- </a> -->
->
<!-- <a href="http://10.10.2.2:5060" target="_blank"> -->10.10.2.2:5060<!-- </a> --></div>
<div>INVITE <a href="http://sip:10301@10.10.2.2:5060" target="_blank">sip:10301@10.10.2.2:5060</a>
SIP/2.0.</div>
<div>Via: SIP/2.0/UDP
10.10.1.1:5060;branch=z9hG4bK3A2284.</div>
<div>Remote-Party-ID: "1112223333" <<a href="mailto:sip%3A1112223333@10.10.1.1" target="_blank"></a><a href="mailto:sip:1112223333@10.10.1.1" target="_blank">sip:1112223333@10.10.1.1</a>>;party=calling;screen=yes;privacy=off.</div>
<div>From: "1112223333" <<a href="mailto:sip%3A1112223333@10.10.1.1" target="_blank"></a><a href="mailto:sip:1112223333@10.10.1.1" target="_blank">sip:1112223333@10.10.1.1</a>>;tag=5745CCC-1C72.</div>
<div>To: <<a href="mailto:sip%3A10301@10.10.2.2" target="_blank">sip:10301@10.10.2.2</a>>.</div>
<div>Date: Thu, 17 Dec 2015 19:20:31 GMT.</div>
<div>Call-ID: <a href="mailto:12968BB5-A42A11E5-8062F2AF-E28C686E@10.10.1.1" target="_blank">12968BB5-A42A11E5-8062F2AF-E28C686E@10.10.1.1</a>.</div>
<div>Supported:
100rel,timer,resource-priority,replaces,sdp-anat.</div>
<div>Min-SE: 1800.</div>
<div>Cisco-Guid:
0311776101-2754220517-2148597785-1445067520.</div>
<div>User-Agent: Cisco-SIPGateway/IOS-12.x.</div>
<div>Allow: INVITE, OPTIONS, BYE, CANCEL,
ACK, PRACK, UPDATE, REFER, SUBSCRIBE,
NOTIFY, INFO, REGISTER.</div>
<div>CSeq: 101 INVITE.</div>
<div>Max-Forwards: 70.</div>
<div>Timestamp: 1450380031.</div>
<div>Contact: <<a href="http://sip:1112223333@10.10.1.1:5060" target="_blank">sip:1112223333@10.10.1.1:5060</a>>.</div>
<div>Expires: 180.</div>
<div>Allow-Events: telephone-event.</div>
<div>Content-Type: application/sdp.</div>
<div>Content-Disposition:
session;handling=required.</div>
<div>Content-Length: 279.</div>
<div>.</div>
<div>v=0.</div>
<div>o=CiscoSystemsSIP-GW-UserAgent 3918
6190 IN IP4 10.10.1.1.</div>
<div>s=SIP Call.</div>
<div>c=IN IP4 10.10.1.1.</div>
<div>t=0 0.</div>
<div>m=audio 18854 RTP/AVP 0 18 101.</div>
<div>c=IN IP4 10.10.1.1.</div>
<div>a=rtpmap:0 PCMU/8000.</div>
<div>a=rtpmap:18 G729/8000.</div>
<div>a=fmtp:18 annexb=no.</div>
<div>a=rtpmap:101 telephone-event/8000.</div>
<div>a=fmtp:101 0-16.</div>
</div>
<div><br>
</div>
<div>Invite messages:</div>
<div><br>
</div>
<div>
<div>U 2015/12/17 14:20:31.546310
<!-- <a href="http://10.10.1.1:50975" target="_blank"> -->10.10.1.1:50975<!-- </a> -->
->
<!-- <a href="http://10.10.2.2:5060" target="_blank"> -->10.10.2.2:5060<!-- </a> --></div>
<div>INFO <a href="http://sip:10301@10.219.136.69:5060" target="_blank">sip:10301@10.219.136.69:5060</a>
SIP/2.0.</div>
<div>Via: SIP/2.0/UDP
10.10.1.1:5060;branch=z9hG4bK3C1EC0.</div>
<div>From: "1112223333" <<a href="mailto:sip%3A1112223333@10.10.1.1" target="_blank"></a><a href="mailto:sip:1112223333@10.10.1.1" target="_blank">sip:1112223333@10.10.1.1</a>>;tag=5745CCC-1C72.</div>
<div>To: <<a href="mailto:sip%3A10301@10.10.2.2" target="_blank">sip:10301@10.10.2.2</a>>;tag=1768D8EC-CCDB1323.</div>
<div>Date: Thu, 17 Dec 2015 19:20:31 GMT.</div>
<div>Call-ID: <a href="mailto:12968BB5-A42A11E5-8062F2AF-E28C686E@10.10.1.1" target="_blank">12968BB5-A42A11E5-8062F2AF-E28C686E@10.10.1.1</a>.</div>
<div>User-Agent: Cisco-SIPGateway/IOS-12.x.</div>
<div>Max-Forwards: 70.</div>
<div>Route:
<sip:10.10.2.2;lr=on;ftag=5745CCC-1C72>.</div>
<div>Timestamp: 1450380031.</div>
<div>CSeq: 103 INFO.</div>
<div>Contact: <<a href="http://sip:1112223333@10.10.1.1:5060" target="_blank">sip:1112223333@10.10.1.1:5060</a>>.</div>
<div>Remote-Party-ID: "WIRELESS CALLER" <<a href="mailto:sip%3A1112223333@10.10.1.1" target="_blank"></a><a href="mailto:sip:1112223333@10.10.1.1" target="_blank">sip:1112223333@10.10.1.1</a>>;party=calling;screen=no;privacy=off.</div>
<div>Content-Length: 0.</div>
<div>.</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Best Regards,</div>
<span><font color="#888888">
<div><br>
</div>
<div>-- </div>
<div>Zahid</div>
<div><br>
</div>
<div>[1] <a href="http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/15-mt/sip-config-15-mt-book/voi-sip-isdn.html#GUID-53D5C9AB-AAC4-4178-8158-0DAEFB5BC33E" target="_blank">http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/15-mt/sip-config-15-mt-book/voi-sip-isdn.html#GUID-53D5C9AB-AAC4-4178-8158-0DAEFB5BC33E</a>
(figure 2 is close to what we are
seeing)</div>
</font></span></div>
<br>
</div>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>