Splendid work Abdul... - Vivek ... View more

There could be many approach to fix this issue, for instance use 'answer-address' to match inbound dial peer and with the help of CoR, you can instruct inbound dial peer to see specific outbound dial peer.  ... View more

Hi Fahim, Location of CUCM cluster doesn't matter. Please check the following link and let us know if you still have any questions. https://supportforums.cisco.com/blog/12539601/trai-india-regulations-voipip-telephony - Vivek ... View more

Many congratulations Chris :) - Vivek ... View more

Hi Diana, NIM card needs PVDM4 to terminate TDM circuit, however any unused channels can be used for transcoding and conference. Motherboard PVDM and extended service module PVDM can also be used for transcoding and conference, but not for TDM. - Vivek ... View more

What I meant is there is no way to route the call back to the cluster in such cases. You always have an option to route the call to other peer outside your cluster when primary peer goes down. - Vivek ... View more

Once call has been discover its route and hits trunk/gateway, there is no provision to route the call back to the cluster. - Vivek ... View more

Can you please let me know which device is assigned 172.20.250.6? Also share the full config in attachment, don't post the configuration here. - Vivek ... View more

Remove the type command and check. - Vivek ... View more

Hi John, You need to carefully play with Answer Too Late Timer which must be less than operator's forward no-answer timer. At the same, you should also take care while adjusting this timer that called party gets enough time to answer the call. Answer Too Late Timer The Answer Too Late timer sets the maximum amount of time a call will be allowed to ring on a Remote Destination. This must be set long enough to give the user a chance to answer the call on the Remote Destination but not too long that the call forwards to the cell phone voicemail. - Vivek ... View more

Our community friend Deji has prepared an excellent document on the same; https://supportforums.cisco.com/document/123061/understanding-output-show-voice-dsp-group-all - Vivek ... View more

Hi Martin, Yes it's possible as I said before but only after matching inbound dial peer and since incoming called-number didn't help us in matching inbound dial peer, please configure URI based command to match dial peer. Once done, we can configure SIP profile to get the called number from TO filed. Please let me know if you face any challenges in configuring the same. - Vivek ... View more

Hi Martin, Since you have configured  incoming called-number 00441524881...$ in dial-peer voice 1 for inbound calls, this dial peer won't match since CUBE fetches called party number from Request-URI and SIPGATE is not sending actual number in Request-URI. Can you change the command to incoming called-number . and see if debug voice ccapi inout gives you an output confirming that dial-peer 1 is being matched. Although I am in the opinion that still it will not work because of presence of character in Request-URI and widlcard in incoming called-number command is limited to matching numerals only. If it works for you let us know so that we can apply further configuration (SIP profile) otherwise use URI based mechanism to match inbound dial peer. Please check the below article how to configure dial peers to match on the basis of URI's. http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-inbnd-dp-match-uri.html I will suggest you to match on the basis of From field which will remain static viz sipgate.co.uk Once we are able to match inbound dial peer, we will have to add some SIP profile commands to fetch the original called party number from To field for further call routing. Please let me know if you have any question. - Vivek ... View more