11-17-2009 12:56 AM - edited 03-13-2019 06:46 PM
at 124-24.T caller id is ok!!
but in 124-24.T2 caller id can't receive at phone.
cfg is the same:
!
voice-port 0/1/0
supervisory disconnect dualtone mid-call
cptone CN
timeouts interdigit 5
timeouts call-disconnect 5
timeouts wait-release 5
caller-id enable
!
try the all caller-id option,can't find the cause!!
caller-id alerting dsp-pre-alloc
caller-id alerting line-reversal
caller-id alerting pre-ring
caller-id alerting ring
at last I found the show voice port is different in 124-24.T and 124-24.T2,when the config is the same:
124-24.T:
Caller ID Info Follows:
Standard BELLCORE <<<
Caller ID is received after 1 ring(s)
124-24.T2:
Caller ID Info Follows:
Standard ETSI <<<xxxx
Caller ID is received after 1 ring(s)
how can I change Caller ID Info Follows:
Standard ETSI ? I already used the cptone CN !!
11-17-2009 05:25 AM
Configure any european cptone and check again.
Or complain to cisco to have the problem fixed.
11-17-2009 05:31 AM
it seems a very strange bug. I have open case and help for tac.
11-17-2009 05:47 AM
It happens all the time.
Cisco fixes something, but breaks something else.
11-17-2009 05:59 AM
but 124-24.T2 and 124-24.T are in the main version,in theory 124-24.T2 will only fix the old bug,but it seems bring the new bug.
11-17-2009 06:04 AM
As mentioned above, new bugs are often introduced in the process of fixing existing ones.
02-05-2010 05:57 PM
TAC answer: to fix a ISDN PRI bug,124-24.T2 has to change Standard ETSI even
using cptone cn,suggest downgrade to 124-24.T,but we are using ssl vpn,124
-24.T has the bug CSCtb73337,we have go to 124-24.T2 to fix CSCtb73337,can't
using caller id a long time.
--we and cisco TAC are crazying for these voice bugs and ssl bugs,it seems
too many bug in cisco voice and security!
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: