cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
906
Views
0
Helpful
8
Replies

CME 3825 ISDN 30 Call Line ID Telco issue

craig.corbett
Level 2
Level 2

Hi All,

Any advice greatly appreciated.

My Telco have told me that they have enabled call line ID (they call it CLIP-Calling Line (Number) Identification Presentation). Apparently this has been enabled for the past two weeks. I have a debug below does this help in determining that 'Clip' is not working or do I need specific configuration etc? this is my first ISDN 30 install (mostly done CME & ISDN2 in the past)

I have configured the translation so that 09 is added so that users can redial missed calls. The users are reporting that only 09 is begin displayed on the phone.

I'm fairly confident with CME just want to make sure 100% that its not my side at fault before I go back to the telco.

Thanks,

Craig.

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Called Party Number i = 0x81, '6687xx'

Plan:ISDN, Type:Unknown

.Jan 20 14:27:02.167: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8001 cal lID = 0x337E switch = primary-net5 interface = User

.Jan 20 14:27:02.179: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x 8001

Channel ID i = 0xA98381

Exclusive, Channel 1

.Jan 20 14:27:02.187: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8 001

Progress Ind i = 0x8188 - In-band info or appropriate now available

.Jan 20 14:27:05.955: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0 x0001

Cause i = 0x8090 - Normal call clearing

.Jan 20 14:27:05.955: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x80 01

.Jan 20 14:27:06.019: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0001

2 Accepted Solutions

Accepted Solutions

Hello Craig,

Try this for translation rule 4:

instead of

voice translation-rule 4

rule 1 // /90/

try

voice translation-rule 4

rule 1 // /90&/

The one you have in place now, takes the incoming calling number, and replaces it with 90. The one that I am asking you to try, takes the incoming calling number and translates to 90 + the incoming number.

Hope that helped, if so please rate.

View solution in original post

Yes I would say so, if you are still getting only 90 to display on the IP phones, then there is no additional incoming digits to manipulate. Also, as stated earlier, I dont see a calling party number in your debug, only the called party number, which says to me that telco may not be sending it. Did you try calling from a different number? It could be that the number you are calling from is unlisted, and therefore is not presented on caller id. Otherwise, I would check with telco. But definitely keep that translation rule in place, because even if telco was sending the number, your translation would have only caused the phones to display only 90.

Hope that helped, if so please rate.

View solution in original post

8 Replies 8

Hello Craig,

What does your translation rule look like? Please post it. Also, it could be a telco issue as I dont see the calling party number presented in the debug.

Thanks,

Hi Kenneth, this is what I have setup:

(Some of it needs to be removed, but shouldn't be the problem .. I hope)

voice translation-rule 1

rule 1 /xxx173/ /4400/

rule 2 /xxx174/ /4401/

rule 3 /xxx175/ /4402/

rule 4 /xxx176/ /4403/

rule 5 /^.*\(....\)/ /\1/

!

voice translation-rule 2

rule 1 /^9/ //

!

voice translation-rule 3

rule 1 /4400/ /xxx173/

rule 2 /4401/ /xxx174/

rule 3 /4402/ /xxx175/

rule 4 /4403/ /xxx176/

!

voice translation-rule 4

rule 1 // /90/

!

voice translation-profile INCOMING

translate calling 4

translate called 1

!

voice translation-profile OUTGOING

translate calling 3

translate called 2

!

voice-port 0/0/0:15

translation-profile incoming INCOMING

translation-profile outgoing OUTGOING

cptone GB

!

Hello Craig,

Try this for translation rule 4:

instead of

voice translation-rule 4

rule 1 // /90/

try

voice translation-rule 4

rule 1 // /90&/

The one you have in place now, takes the incoming calling number, and replaces it with 90. The one that I am asking you to try, takes the incoming calling number and translates to 90 + the incoming number.

Hope that helped, if so please rate.

Hi,

Thanks for the suggestion, I have changed the translation-rule as per your recommendation but still the same issue. I guess it is a Telco issue?

Yes I would say so, if you are still getting only 90 to display on the IP phones, then there is no additional incoming digits to manipulate. Also, as stated earlier, I dont see a calling party number in your debug, only the called party number, which says to me that telco may not be sending it. Did you try calling from a different number? It could be that the number you are calling from is unlisted, and therefore is not presented on caller id. Otherwise, I would check with telco. But definitely keep that translation rule in place, because even if telco was sending the number, your translation would have only caused the phones to display only 90.

Hope that helped, if so please rate.

Thanks Kenneth.

Thanks Craig for the nice ratings and I wish you success in getting your issue resolved!!

Just a follow-up, this was a Telco issue. It has now been fixed.

Just in case someone else has the same issue, this is what you should see at the terminal. Note the line: Calling Party Number i = 0x2183, '1111605xxx'

---

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Calling Party Number i = 0x2183, '1111605xxx'

Plan:ISDN, Type:National

Called Party Number i = 0x81, '668xxx'

Plan:ISDN, Type:Unknown

.Jan 21 14:32:51.881: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8001 callID = 0x3403 switch = primary-net5 interface = User

.Jan 21 14:32:51.893: ISDN Se0/0/0:15 Q931: TX ->

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: