Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
588
Views
25
Helpful
9
Replies

Trunk to Trunk rerouting through PRI CUCM

shakim001
Level 1
Level 1

‎01-28-2022 11:45 AM

Dears,

I would like to reroute incoming call to a specific number on PRI to a mobile number through same PRI circuit, 

I configured the following

call routing> Translation pattern>

Translation Pattern : 50 //DID number

Called Party Transform Mask : 901002713555 //9 prefix and 01002713555 is mobile number

------------------------------------------------

when I test the call I received the following error on the debug with red, however if I call from internal set the call is working 

So any advice

Jan 28 19:20:27.994: ISDN Se0/2/0:15 Q931: SETUP pd = 8  callref = 0x0353
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18392
                Preferred, Channel 18
        Calling Party Number i = 0x0183, '01002713466'
                Plan:ISDN, Type:Unknown
        Called Party Number i = 0xC1, '52'
                Plan:ISDN, Type:Subscriber(local)
Jan 28 19:20:27.994: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=22
Jan 28 19:20:28.007: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=21 nr=22
Jan 28 19:20:28.008: ISDN Se0/2/0:15 Q931: SETUP pd = 8  callref = 0x0004
        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 = 0x0883, '20225876359'
                Plan:National, Type:Unknown
        Called Party Number i = 0x88, '01002713555'
                Plan:National, Type:Unknown
Jan 28 19:20:28.024: ISDN Se0/2/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=22
Jan 28 19:20:28.121: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=22 nr=22
Jan 28 19:20:28.121: ISDN Se0/2/0:15 Q931: SETUP_ACK pd = 8  callref = 0x8004
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Jan 28 19:20:28.121: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=23
Jan 28 19:20:28.122: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=22 nr=23
Jan 28 19:20:28.123: ISDN Se0/2/0:15 Q931: STATUS pd = 8  callref = 0x0004
        Cause i = 0x80E2 - Message not compatible with call state or not implemented
        Call State i = 0x01
Jan 28 19:20:28.130: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=23 nr=22
Jan 28 19:20:28.131: ISDN Se0/2/0:15 Q931: CALL_PROC pd = 8  callref = 0x8004
Jan 28 19:20:28.131: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=24
Jan 28 19:20:28.132: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=23 nr=24
Jan 28 19:20:28.132: ISDN Se0/2/0:15 Q931: STATUS pd = 8  callref = 0x0004
        Cause i = 0x80E0 - Mandatory information element missing
        Call State i = 0x01
Jan 28 19:20:28.133: ISDN Se0/2/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=23
Jan 28 19:20:28.143: ISDN Se0/2/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=24
Jan 28 19:20:28.243: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=24 nr=24
Jan 28 19:20:28.243: ISDN Se0/2/0:15 Q931: DISCONNECT pd = 8  callref = 0x8004
        Cause i = 0x82E500000000 - Message not compatible with call state
        Progress Ind i = 0x8288 - In-band info or appropriate now available
0 Helpful
9 Replies 9

Roger Kallberg
VIP
VIP

‎01-29-2022 11:36 PM

Likely this could be caused by that your service provider does not allow calls from calling numbers that are outside of the assigned DID number range that you have. To check if this is your problem trying to mask the calling number on the call to one of your assigned DID numbers and make the call. If this works and you want to be able to pass the original calling number on these calls you’ll need to reach out to your service provider to discuss if they have the option to allow you to pass non assigned numbers.



Response Signature


0 Helpful

shakim001
Level 1
Level 1
In response to Roger Kallberg

‎01-30-2022 01:07 AM 

 Calling Party Number i = 0x0883, '20225876359'

 Thanks for your update Roger, in Fact I've already tried to mask the outgoing call as seen in the previous trace by number 20225876359 which is already in the DID range, However this is not working

Roger Kallberg
VIP
VIP
In response to shakim001

‎01-30-2022 01:10 AM - edited ‎01-30-2022 01:18 AM

This information would have been helpful if you would have shared it upfront. We can not know the specifics of your setup if you do not share it. Can you please post the output from a working call made from an internal number so that we can compare the two?



Response Signature


shakim001
Level 1
Level 1
In response to Roger Kallberg

‎01-30-2022 01:47 AM 

Jan 26 11:56:01.103: ISDN Se0/2/0:15 Q921: User RX <- RRp sapi=0 tei=0 nr=65
Jan 26 11:56:01.103: ISDN Se0/2/0:15 Q921: User TX -> RRf sapi=0 tei=0 nr=51
Jan 26 11:56:07.683: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=65 nr=51
Jan 26 11:56:07.683: ISDN Se0/2/0:15 Q931: SETUP pd = 8  callref = 0x0005 
	Bearer Capability i = 0x8090A3 
		Standard = CCITT 
		Transfer Capability = Speech  
		Transfer Mode = Circuit 
		Transfer Rate = 64 kbit/s 
	Channel ID i = 0xA98381 
		Exclusive, Channel 1 
	Display i = 'Head of IT' 
	Calling Party Number i = 0x0881, '20225876355' 
		Plan:National, Type:Unknown 
	Called Party Number i = 0x88, '01007774877' 
		Plan:National, Type:Unknown
Jan 26 11:56:07.698: ISDN Se0/2/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=66
Jan 26 11:56:07.828: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=51 nr=66
Jan 26 11:56:07.829: ISDN Se0/2/0:15 Q931: SETUP_ACK pd = 8  callref = 0x8005 
	Channel ID i = 0xA98381 
		Exclusive, Channel 1
Jan 26 11:56:07.829: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=52
Jan 26 11:56:08.271: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=52 nr=66
Jan 26 11:56:08.271: ISDN Se0/2/0:15 Q931: ALERTING pd = 8  callref = 0x8005 
	Progress Ind i = 0x8288 - In-band info or appropriate now available 
Jan 26 11:56:08.271: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=53
Jan 26 11:56:18.233: ISDN Se0/2/0:15 Q921: User RX <- RRp sapi=0 tei=0 nr=66
Jan 26 11:56:18.233: ISDN Se0/2/0:15 Q921: User TX -> RRf sapi=0 tei=0 nr=53
Jan 26 11:56:22.521: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=66 nr=53
Jan 26 11:56:22.522: ISDN Se0/2/0:15 Q931: DISCONNECT pd = 8  callref = 0x0005 
	Cause i = 0x8090 - Normal call clearing
Jan 26 11:56:22.531: ISDN Se0/2/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=67
Jan 26 11:56:22.739: ISDN Se0/2/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=53 nr=67
Jan 26 11:56:22.739: ISDN Se0/2/0:15 Q931: RELEASE pd = 8  callref = 0x8005
Jan 26 11:56:22.740: ISDN Se0/2/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=54
Jan 26 11:56:22.745: ISDN Se0/2/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=67 nr=54
Jan 26 11:56:22.745: ISDN Se0/2/0:15 Q931: RELEASE_COMP pd = 8  callref = 0x0005

this is a working call from internal set which DID is 20225876355 to call Mobile Number 01007774877

Roger Kallberg
VIP
VIP
In response to shakim001

‎01-30-2022 03:27 AM - edited ‎02-03-2022 06:09 AM

Apart from the calling and called numbers the only thing that I see that differs is this.

 

Calling Party Number i = 0x0881, '20225876355'

Plan:National, Type:Unknown

Called Party Number i = 0x88, '01007774877'

Plan:National, Type:Unknown

 

Calling Party Number i = 0x0883, '20225876359'

Plan:National, Type:Unknown

Called Party Number i = 0x88, '01002713555'

Plan:National, Type:Unknown

A 3 at the end usually indicates that the calling number is screened.



Response Signature


shakim001
Level 1
Level 1
In response to Roger Kallberg

‎02-03-2022 05:04 AM

Hi Roger,

 

I've tried with many different scenarios to change the Calling Party Transform Mask, however no succeeded trials,

 

So do you have any idea or a specific configuration, also if you would like to share the configurations with you, let me know,

 

Regards

Sherif

0 Helpful

Roger Kallberg
VIP
VIP
In response to shakim001

‎02-03-2022 06:19 AM

Not sure what control protocol you use for your PRI connections from CM, so not sure if the screenshot will match for you, but you might want to try sending redirecting diversion information to your service provider. For a SIP controlled connection it would look like this.

image.png

Please share you configuration here, with redacted of any sensitive information for us to be able to verify what you have setup.



Response Signature


0 Helpful

shakim001
Level 1
Level 1
In response to Roger Kallberg

‎02-03-2022 07:01 AM

Hi Roger,

 

Not working the checkbox, I've attached the full configuration for PRI,

 

Thanks

Sherif

Preview file
254 KB

Roger Kallberg
VIP
VIP
In response to shakim001

‎02-03-2022 10:20 AM

As far as I can see you do not have the outbound redirecting number delivery set.



Response Signature


0 Helpful
Customers Also Viewed These Support Documents