12-02-2016 06:27 AM - edited 03-17-2019 08:50 AM
12-02-2016 07:26 AM
Is this CUCM?? CME??
What do you use for PSTN??
Have you already compared the debugs of both calls??
12-02-2016 09:46 AM
Thanks for your reply Jamie ! phones are registered to cucm which is at DC. for pstn one e1 is terminated at local GW at the site. if we reach via pstn then there is no issue and calls are forwarded properly. Issue is only while reaching extension over the WAN. And I have not compared any logs as frankly I am not aware of which debugs to compare.
12-04-2016 05:21 PM
My gut feeling is, this is CSS related, and more precisely, your call forward CSS's.
make sure that these call forward CSS's can call mobile numbers.
quickest way to test is to use Dialed Number analyzer, or stick a test phone's line into a call forward CSS and call a mobile number and see if it established the call
12-04-2016 07:12 PM
Yes first of all I checked that however Call forward css and line css is same and the extension can call mobile numbers directly the issue only in case of forwarding
12-04-2016 07:19 PM
if you are using 0 or 9 for an "outside line" do you have that in the CFWD All number as well?
also, what gateway are you using to make that forwarded call to a mobile? is it possible to send the debugs of a failing call, like ccsip message, debug dial-peer.
cheers
12-04-2016 09:36 PM
For outside line we dial 0 and yes whlile forwarding we are adding 0 prefix that is the reason it is getting reached if you try to call via pstn.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: