cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1291
Views
25
Helpful
9
Replies

From External Call Forward is not using the correct Caller id Mask

Hello,

 

i'm configuring Call forwarding Caller id from external, but when i call from the external the outbound call have as Calling the original caller id.

 

If i change to First (or last) redirect i see the DN as Caller id also if is present a Calling Transformation Pattern to match XXXX and add prefix for the call:

 

 

debug with originator:

 

DN: 2341

calling number: 3481111111

called number: 0106471111

redirected: 3453111111

 

Dec  4 16:06:41.405: ISDN Se0/1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x60F7 
        Cause i = 0x8A90 - Normal call clearing
Dec  4 16:06:41.412: ISDN Se0/1/0:15 Q931: TX -> RELEASE pd = 8  callref = 0xE0F7
Dec  4 16:06:41.461: ISDN Se0/1/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x60F7
Dec  4 16:08:14.219: ISDN Se0/1/0:15 Q931: TX -> 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 = 0xA9839F 
                Exclusive, Channel 31 
        Calling Party Number i = 0x0183, ' 3481111111 '
                Plan:ISDN, Type:Unknown 
        Called Party Number i = 0x80, '3453111111' 
                Plan:Unknown, Type:Unknown
Dec  4 16:08:14.254: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8004 
        Channel ID i = 0xA9839F 
                Exclusive, Channel 31
 
 
 
 
if i set First (or last) redirect external:
 
 
Dec  4 17:27:34.131: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0001 
        Sending Complete 
        Bearer Capability i = 0x8090A3 
                Standard = CCITT 
                Transfer Capability = Speech  
                Transfer Mode = Circuit 
                Transfer Rate = 64 kbit/s 
        Channel ID i = 0xA9839F 
                Exclusive, Channel 31 
        Calling Party Number i = 0x0080, '2341' 
                Plan:Unknown, Type:Unknown 
        Called Party Number i = 0x80, '3453111111' 
                Plan:Unknown, Type:Unknown
Dec  4 17:27:34.165: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8001 
        Channel ID i = 0xA9839F 
                Exclusive, Channel 31
 
 
 
Calls from internal to external is work fine as expected.
Calls from internal, forwarded to external is working as expected.
 
The issue is only when the caller is from external.
 
It should match the Transformation patter as for the internal to external, but without success. (attached)
 
Thanks!
9 Replies 9

Can you please share an outline of an internal forwarded to external, that you say is working as expected, with all details on all the calling/called/forwarded numbers and the output of Q931 debug?



Response Signature


Hello Roger and i add that the gateway is in MGCP configuration and now is set as "Originator", since i need to let works for now until the final solution.

 

If i set as originator and the caller id of the redirect flow is 3481111111, it match a Transformation patter (attached) copied from the XXXX i showed you.

 

So is strange that it not match the XXXX on the same partition/css as the 0.! since is the same flow.

It seems that when is set First redirect it bypass the transformation pattern on the flow.

 

Caller: DN 2341

Called: DN 2485

Redirect to 3481111111

 

Dec 5 08:55:23.655: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0002
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Calling Party Number i = 0x0081, '010***2341' (masked for privacy)
Plan:Unknown, Type:Unknown
Called Party Number i = 0x81, '3481111111'
Plan:ISDN, Type:Unknown
Dec 5 08:55:23.679: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8002
Channel ID i = 0xA9839F
Exclusive, Channel 31
Dec 5 08:55:27.418: ISDN Se0/1/0:15 Q931: RX <- PROGRESS pd = 8 callref = 0x8002
Progress Ind i = 0x8288 - In-band info or appropriate now available
Dec 5 08:55:27.455: ISDN Se0/1/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8002
Progress Ind i = 0x8288 - In-band info or appropriate now available
Dec 5 08:55:33.183: ISDN Se0/1/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x8002
Connected Number i = 0x00C3
UNRECOGNIZED VARIABLE (0x76) i = 0x00C0
Dec 5 08:55:33.200: ISDN Se0/1/0:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0002

Thanks, that’s what I did expect. For your internal call the calling number is 2341, this is why it matches the transformation. Whereas when you get an external call and forward it to an external number the calling number that hits the route pattern is that of the external calling party. This would not be a match for your transformation. So the system is operating as expected. Changing the setting for what number to show for redirected calls happens on the gateway or trunk configuration object and that’s later than where the transformation takes place. A transformation is always matched on the information that is received on the route pattern level, ie multiple steps before the gateway/trunk in the call routing logic.



Response Signature


Ok Roger so what is your suggestion about, where i have to modify ora add settings to resolve? cause i had a lot of troubleshooting and also TAC about 5 hours didn’t notice the issue.

 

thanks a lot

I would think that your opinion would be to use translation rules on the gateway, but that requires you to change the control protocol for your gateway from MGCP to either SIP or H.323, where SIP would be the preferred.



Response Signature


Hello Roger,

 

is not possible to manage without to change the protocol?

since is in production and i can't reorganize all in time.

Or i can use both protocol to manage the flow for the forwarded call from outside in SIP and the other in mgcp?

 

Thanks

No you cannot use both protocols. I have some far away record that you might be able to put the voice translation profile on the voice port(s) and have it modify your called/calling number even if you use MGCP. But it’s nothing I’ve used or done myself. It’s been a long time since I used MGCP, we moved to SIP about 8-9 years ago.



Response Signature


Hello Roger,

 

clear i cant manipulate number on vg in mgcp

 

But i'm feeling so bad that is so strange on a Cucm 14, is not possible to do something so "easy" to change the callerid of a call passing through itself...

 

also why, since is using the translation pattern when the caller id is on originator, why it not use when on First redirect number, is on the same segment?

 

If i use the IE Redirect Number on outbound, i cleary see that the voicegateway is receiving the right translated caller id number but i cant differentiate on DN base in that case so is not useful.

 

There is a workaround i can use to force the callerid using the Redirect Number IE?

 

Thanks

 

 

 

 

You would have to use calling party transformation rules in CM to change the calling party number. There are also changes that can be made on the translation pattern or route pattern (whichever is applicable, could be both) and in the route details (intersection of route list and route group). I think you best bet would be to look at the calling party transformation CSS and the related calling party transformation patterns.