cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1243
Views
0
Helpful
4
Replies

CTS not calling C series running Software TC5

Zawlatt456
Level 1
Level 1

I am having a problem where calls from CTS is not calling to Tangberd C series running software version TC5.1.

Following is the set up;

CTS registered to CUCM and C series registered to the VCS

there is a trunk between CUCM and VCS.

Version,

CTS-1.8.1, C sereis-TC5.1, CUCM 8.6.2, VCS 7.1

CTS is not making a call to the TC5 endpoint but if i downgrade it to TC4. the call goes thru.

Anybody's run into this kind of issue? if you do, can you share me your solution please?

1 Accepted Solution

Accepted Solutions

Paul Anholt
Cisco Employee
Cisco Employee

Hi Zaw,

I have seen an issue similar to this in the past on CUCM 8.6.2 where the TC5 endpoint sents a URI in the SIP contact header and the CUCM attempts a DNS lookup on the server portion of the URI which fails and the call tears down.

I would need to see CUCM traces to confirm this is the issue, but if I recall correctly the CTS endpoint would receive a 503 Service unavailable message.

If you control the DNS server the CUCM is pointed to then you could try to add a bogus A record that matches your SIP domain on the VCS to see if it helps.

It might be best to open a TAC case to explore all your options.

Thanks,

Paul

View solution in original post

4 Replies 4

crisalex
Cisco Employee
Cisco Employee

Hi,

Can you notice any diference in term of C codec configuration after the upgrade? can I take a look at the xconf/xstatus from the codec on TC4.x and on TC5.x ( working / non working case) ?

Regards

jusstone
Level 1
Level 1

It would also be good to know what the behavior is during the failure. Is there any initial setup, or does it fail immediately? Is there any specific error on the screen when it fails?

Paul Anholt
Cisco Employee
Cisco Employee

Hi Zaw,

I have seen an issue similar to this in the past on CUCM 8.6.2 where the TC5 endpoint sents a URI in the SIP contact header and the CUCM attempts a DNS lookup on the server portion of the URI which fails and the call tears down.

I would need to see CUCM traces to confirm this is the issue, but if I recall correctly the CTS endpoint would receive a 503 Service unavailable message.

If you control the DNS server the CUCM is pointed to then you could try to add a bogus A record that matches your SIP domain on the VCS to see if it helps.

It might be best to open a TAC case to explore all your options.

Thanks,

Paul

Zawlatt456
Level 1
Level 1

Thanks everyone for your reponsens. The issue has been solved. the problem was CUCM was doing a DNS lookup aganist the domain name that is sent back by the VCS.

this is a cucm bug. as far as i know the fix is applied in cucm 9.0 (1).

the workaround is to create a srv record in the DNS server that translates that domain to the VCS ip address.

Getting Started

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: