Hello, I'm running into the exact same issue as Aamir does. If you make a debug ccsip messages of such a call, you don't see any sip response back to the cme sip phone when the call is answered at hq...,
I changed the signalling from h323 to sip and everything works just fine, I was wondering if the reason why this call is failing is by the following statement: "SIP endpoints are not supported on H.323 trunks. SIP endpoints are supported on SIP trunks only. " source:cme config guide http://cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmebasic.html Any advice appreciated, Otto Mensaje original----- De: ccie_voice-boun...@onlinestudylist.com en nombre de Aamir Panjwani Enviado el: mar 26/05/2009 18:39 Para: Larry Hadrava CC: ccie_voice@onlinestudylist.com Asunto: Re: [OSL | CCIE_Voice] V3: Lab4A Gatekeeper scenario Thanks for your response Larry. When I call from CME SIP to any phone in HQ via gatekeeper it rings on HQ phone but when I lift the handset or press answer soft key it stops ringing on HQ phone (but "answer" key is still displayed on the HQ phone) and at the same time it is ringing on calling phone (CME SIP) with "ring out" on the display for 3 rings and then it eventually disconnects. There is no VM setup involve and it works fine without gatekeeper. I have testing above in my own lab, however, I ran into exactly same problem when I had a proctor lab session last Saturday. So calling from CME SIP (XLite) to HQ SIP (CIPC) same problem. What is even more interesting is when I loaded final config of lab 4A in which everything meant to be working I still had a same problem! and yes I did "revert entire pod" before loading final lab 4A Many Thanks From: Larry Hadrava [mailto:lar...@ipexpert.com] Sent: Wednesday, 27 May 2009 8:47 AM To: Aamir Panjwani Cc: ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] V3: Lab4A Gatekeeper scenario Aamir: So, from the description, when calling from the SIP phone, the call goes through and you answer the call but the SIP device does not show as connected? Does it keep ringing of does it eventually go to VM? I'm just wondering where the problem is - on the calling or called end. Sounds like that some supervisory signaling is not being passed properly. Are you doing this lab on a Proctor labs rack? Does this setup work without the gatekeeper? Thanks Larry Hadrava CCIE #12203 CCNP CCNA Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com On Tue, May 26, 2009 at 6:41 PM, Aamir Panjwani <aamir.panjw...@ivision.com.au> wrote: Guys any idea regarding below issue please? From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Aamir Panjwani Sent: Tuesday, 26 May 2009 6:23 PM To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] V3: Lab4A Gatekeeper scenario Hi All, As per lab 4A I have setup a GK trunk between CUCM and CME and I got following problem. When I call from CME SIP phone (7961) to SCCP or SIP phone (7961) at HQ it rings on HQ phone but when I answer the call it is still ringing out on calling party (CME SIP). Other way around is just fine. Also, calling from CME SCCP to HQ SIP or SCCP is fine too. My config is similar to proctor guide solution. Has anyone else ran into this problem before? Thanks Aamir ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
