cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
876
Views
5
Helpful
7
Replies

From 7821 phone unable to make external calls

Syed
Level 3
Level 3

Dear All,

I have 7821 phones registered with CUCM 8.5.1, but unable to make OffNet calls over SIP trunk, getting fast busy tone after keying in client matter code.

Other phones with identical CSS & Partition and CMC are able to get through.

What could be the cause?

Thank you in advance

2 Accepted Solutions

Accepted Solutions

Syed

Logs are not in detailed pull the detailed logs, Here what i see for this call getting CANCEL message

2016/05/05 12:28:50.916|SIPL|0|TCP|IN|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430677^10.130.31.83^*|1560956|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|INVITE
2016/05/05 12:28:50.917|SIPL|0|TCP|OUT|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430677^10.130.31.83^*|1560957|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|100 Trying
2016/05/05 12:28:50.920|CC|SETUP|76258056|76258057|814003|814001|814001
2016/05/05 12:28:50.922|SIPL|76258057|TCP|OUT|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430677^10.130.31.83^SEPB07D47D1008C|1560958|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|INVITE
2016/05/05 12:28:50.932|SIPL|76258057|TCP|IN|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430678^10.130.31.49^*|1560959|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|100 Trying
2016/05/05 12:28:51.027|SIPL|76258057|TCP|IN|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430679^10.130.31.49^*|1560960|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|180 Ringing
2016/05/05 12:28:51.029|SIPL|76258056|TCP|OUT|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430679^10.130.31.49^*|1560961|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|180 Ringing
2016/05/05 12:28:52.182|CC|RELEASE|76258020|76258021|16
2016/05/05 12:28:52.998|SIPL|76258056|TCP|IN|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430681^10.130.31.83^*|1560964|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|CANCEL

Br, Nadeem Please rate all useful post.

View solution in original post

Hi Syed,

You pasted the call logs instead of the SDL traces so the info was not present in the logs. However if the issue went way after phone reset then it most likely was a database issue which is generally fixed by reset or devices or services which allow them to download the latest config file.

Manish

View solution in original post

7 Replies 7

Manish Gogna
Cisco Employee
Cisco Employee

Hi Syed,

Can you check if the 7821 is able to make calls to outside numbers through route patterns which are not CMC enabled. If yes, then you should get a detailed callmanager service trace for a test call.

Manish

Hello Manish,

Yes, it is working with non CMC route patterns.

Please find the attached call logs.

sorry for incomplete info

Calling number: 814003

Mac-address: SEPB07D47D1008C

Syed

Logs are not in detailed pull the detailed logs, Here what i see for this call getting CANCEL message

2016/05/05 12:28:50.916|SIPL|0|TCP|IN|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430677^10.130.31.83^*|1560956|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|INVITE
2016/05/05 12:28:50.917|SIPL|0|TCP|OUT|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430677^10.130.31.83^*|1560957|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|100 Trying
2016/05/05 12:28:50.920|CC|SETUP|76258056|76258057|814003|814001|814001
2016/05/05 12:28:50.922|SIPL|76258057|TCP|OUT|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430677^10.130.31.83^SEPB07D47D1008C|1560958|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|INVITE
2016/05/05 12:28:50.932|SIPL|76258057|TCP|IN|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430678^10.130.31.49^*|1560959|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|100 Trying
2016/05/05 12:28:51.027|SIPL|76258057|TCP|IN|10.130.209.10|5060|SEPB07D47D10143|10.130.31.49|52211|4,100,57,1.430679^10.130.31.49^*|1560960|c53e7a80-72b11252-953a-ad1820a@10.130.209.10|180 Ringing
2016/05/05 12:28:51.029|SIPL|76258056|TCP|OUT|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430679^10.130.31.49^*|1560961|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|180 Ringing
2016/05/05 12:28:52.182|CC|RELEASE|76258020|76258021|16
2016/05/05 12:28:52.998|SIPL|76258056|TCP|IN|10.130.209.10|5060|SEPB07D47D1008C|10.130.31.83|49610|4,100,57,1.430681^10.130.31.83^*|1560964|b07d47d1-008c0015-0c200477-6c2f5d78@10.130.31.83|CANCEL

Br, Nadeem Please rate all useful post.

Hi Nadeem/Manish,

I reset all the 7821s and it started working. I am not sure what was wrong??

Hi Syed,

You pasted the call logs instead of the SDL traces so the info was not present in the logs. However if the issue went way after phone reset then it most likely was a database issue which is generally fixed by reset or devices or services which allow them to download the latest config file.

Manish

Thank you guys 

Since, I am the only voip engineer in this organisation and with your spontaneous help & support I do not feel that I am alone.

This forum is amazingly good....