Hi Nick,<br><br>You are right. <br>The provider sent me their configuration and it seems they are using UDP. They changed it to TCP and we test the call and looks promising.<br><br>Thanks for all the help!<br><br>cheers,<br>
jeff<br><br><div class="gmail_quote">On Fri, Mar 5, 2010 at 10:51 PM, Nick Matthews <span dir="ltr"><<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
CUCM will not automatically attempt UDP, you will have to instruct it<br>
to use it. You may see a TCP packet to port 5060 instead of a SIP<br>
invite if the other device does not support TCP SIP. The difference<br>
could be that CUBE does support TCP and it explains what you're<br>
seeing.<br>
<font color="#888888"><br>
-nick<br>
</font><div><div></div><div class="h5"><br>
On Fri, Mar 5, 2010 at 12:29 AM, Jefflin Choi <<a href="mailto:jefflin.choi@gmail.com">jefflin.choi@gmail.com</a>> wrote:<br>
> Hi Nick,<br>
><br>
> My apologies for the confusion.<br>
><br>
> Let me ellaborate further the diagram and description as i came to<br>
> understand it further from time to time asking the provider.<br>
><br>
> ip phone(skinny)---CCM7------SBC-------Huawei proxy server.<br>
><br>
> The SBC suppose to be the one to control over the signaling and usually also<br>
> the media streams involved in setting up the communication. Our CCM does<br>
> have ip connectivity to the SBC only and not the huawei device. Shouldn't it<br>
> act like a CUBE so we don't need connectivity to the public.<br>
><br>
> Regarding the sip invite, i was refering to the initial SIP INVITE requests<br>
> sent by the CCM7 via sip trunk since the call came from 7961 ip phones<br>
> registered using SCCP on CCM7. The 7961 phone calls out. CCM7 suppose to<br>
> initiate SIP invite request to the configured ip address(SBC ip) on the sip<br>
> trunk.<br>
><br>
> If trunk is configured to point to the CUBE(cisco router 10.10.10.2) then i<br>
> sniff the packet on the CCM(10.10.10.1). The sniffer trace has 10.10.10.1<br>
> Source address - 10.10.10.2 Destination address SIP invite.<br>
><br>
> If however the trunk is configured to point to the SBC directly, i see no<br>
> SIP invite request initiated by the Callmanager on the sniffer trace and<br>
> also the provider claims that he is not seeing any request comming from the<br>
> CCM7 on their SBC.<br>
><br>
> If the SBC or huawie does support only UDP, shouldn't i suppose to see SIP<br>
> invite request via UDP porton the sniffer trace generated by the CCM? In<br>
> the case CCM7 trunking directly to SBC without CUBE, i see no sip invite<br>
> requested when cisco ip phones tried to make outgoing calls.<br>
><br>
> I hope this clarifies the confusion.<br>
><br>
> thanks,<br>
> Jeff<br>
><br>
> On Thu, Mar 4, 2010 at 10:52 PM, Nick Matthews <<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>> wrote:<br>
>><br>
>> I'm still confused on what you mean by no SIP invite.<br>
>><br>
>> It's possible that the huawei only supports UDP SIP and it's not<br>
>> completing the 3 way TCP handshake. You can change that under the SIP<br>
>> profiles to be UDP only.<br>
>><br>
>> Otherwise, check that huawei has routing back to the IP of your CUCM,<br>
>> and firewalls aren't involved.<br>
>><br>
>> -nick<br>
>><br>
>> On Thu, Mar 4, 2010 at 3:38 AM, Jefflin Choi <<a href="mailto:jefflin.choi@gmail.com">jefflin.choi@gmail.com</a>><br>
>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > Thanks for all the reply.<br>
>> ><br>
>> > Tried placing the a CUBE in the middle and seems like there is already<br>
>> > SIP<br>
>> > invite being sent. Too bad the huawei isn't full configured yet to<br>
>> > determine<br>
>> > if all is ok.<br>
>> ><br>
>> > I was wondering....I tried to make a test call using SIP trunk directly<br>
>> > to<br>
>> > the B2B SBC and no sip invite. But i did get sip invite when i pointed<br>
>> > it to<br>
>> > the cube.<br>
>> > All i can see on the sniff trace from CCM to B2B is:<br>
>> > TCP 35472 > sip [SYN] seq=0 Win 5840 Len=0 MSS=1460 TSV=82731827 TSER=0<br>
>> > WS=2<br>
>> ><br>
>> > In fact i just changed the ip of the CUBE to the B2B SBC to make sure<br>
>> > configs are exactly the same but no sip invite unlike when it is pointed<br>
>> > to<br>
>> > the CUBE. Is this normal? Any thoughts?<br>
>> ><br>
>> > Thanks,<br>
>> > Jeff<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Thu, Mar 4, 2010 at 1:10 AM, Mark Holloway <<a href="mailto:mh@markholloway.com">mh@markholloway.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> You most certainly need CUBE. You can find the CUBE guide for<br>
>> >> sip-to-sip<br>
>> >> here.<br>
>> >><br>
>> >><br>
>> >> <a href="http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html" target="_blank">http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html</a><br>
>> >><br>
>> >><br>
>> >> On Mar 3, 2010, at 7:18 AM, Jefflin Choi wrote:<br>
>> >><br>
>> >> I see. So a router in the middle is required then. Doesn't the CCM7<br>
>> >> support it without the CUBE?<br>
>> >><br>
>> >> Thanks.<br>
>> >><br>
>> >> On Wed, Mar 3, 2010 at 9:48 PM, Dennis Heim <<a href="mailto:Dennis.Heim@cdw.com">Dennis.Heim@cdw.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> You will probably end up having to use CUBE, instead of terminating<br>
>> >>> the<br>
>> >>> trunk to CCM.<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> Dennis Heim<br>
>> >>> Network Voice Engineer<br>
>> >>> CDW Advanced Technology Services<br>
>> >>> 11711 N. Meridian Street, Suite 225<br>
>> >>> Carmel, IN 46032<br>
>> >>><br>
>> >>> 317.569.4255 Office<br>
>> >>> 317.569.4201 Fax<br>
>> >>> 317.694.6070 Cell<br>
>> >>><br>
>> >>> <a href="mailto:dennis.heim@cdw.com">dennis.heim@cdw.com</a><br>
>> >>> <a href="http://www.berbee.com" target="_blank">www.berbee.com</a><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
>> >>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Jefflin Choi<br>
>> >>> Sent: Wednesday, March 03, 2010 8:31 AM<br>
>> >>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> >>> Subject: [cisco-voip] CCM SIP connection to B2B getting fast busy<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> Hi,<br>
>> >>><br>
>> >>> I'm trying to configure a SIP connection to a 3rd party B2B SIP<br>
>> >>> device,<br>
>> >>> then B2B will relay to a Huawei (SIP) device on the other end.<br>
>> >>> topology:<br>
>> >>> IP Phones ------CCM7 -------(provider)--B2B---------Huawei---pstn<br>
>> >>><br>
>> >>> configuration:<br>
>> >>> CCM is configured with SIP trunk with ip address of the B2B and route<br>
>> >>> pattern uses the SIP trunk configured. MTP required uncheck as of the<br>
>> >>> moment. codec G711uLaw and No authentication required.<br>
>> >>><br>
>> >>> Problem:<br>
>> >>> Outgoing call from IP Phone to PSTN gets fast busy signal. When<br>
>> >>> placed a<br>
>> >>> sniffer in between CCM7 and B2B gateway, i didnt see any sip invite<br>
>> >>> initiated by the CCM7. CCM7 and ip phones only have traffic<br>
>> >>> reachability to<br>
>> >>> B2B but not Huawei.<br>
>> >>> The provider (B2B to pstn) was tested using altitude(as claimed by the<br>
>> >>> customer) and works fine but we are testing using CCM7.<br>
>> >>><br>
>> >>> Question:<br>
>> >>> 1> Am i right to use CCM trunk to connect to the B2B sip?<br>
>> >>> 2> Any additional configs i need to configure? Misconfiguration?<br>
>> >>> 3>Should i expect SIP invite to be sent by CCM when call is triggered<br>
>> >>> by<br>
>> >>> ip phones?<br>
>> >>><br>
>> >>> Thanks,<br>
>> >>> Jeff<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> cisco-voip mailing list<br>
>> >> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> >> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > cisco-voip mailing list<br>
>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br>