CME-2921 ISR- receivers see default number & not the actual caller id

[BalSun]

Hi all,

the users at one of our site(A) have setup call fwd on their desk phones to their mobile numbers. If some one calls the desk phone which has call fwd setup the receiver sees the default number 1803 instead of the actual caller id. This happens only to the calls from the external numbers including other sites and not calls from site A.  sharing the sip-profile config below.

!
voice class sip-profiles 1
request CANCEL sip-header Max-Forwards modify ".*" "User-Agent: CUBE"
response ANY sip-header Remote-Party-ID modify "(.*@).*>(.*)" "\1xyz.org.au>\2"
request ANY sip-header Remote-Party-ID modify "(.*@).*>(.*)" "\1xyz.org.au>\2"
request INVITE sip-header P-Asserted-Identity modify "(.*)" "P-Asserted-Identity: <sip:NxxxxxR@xyz.org.au>"
request INVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:xxxx1803@xyz.org.au>"
request REINVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:xxxx1803@xyz.org.au>"
request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv"
request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv"

I modified the sip-header diversion config to this which resulted in call fwd not working on all the devices so had to roll back.

request INVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:\1@xyz.org.au>"
request REINVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:\1@xyz.org.au>"

I would like the receiver who has enabled call fwd to the mobile phones to see the actual caller id but i want the outgoing calls to show 1803 at the receiving end. This is an aged care facility and the inmates change often, we do not want the previous inmates friends or relatives calling the room directly while the inmate has been shifted to other room or moved out. 

[b.winter]

My first guess would be: Is "CLIP no screening" enabled for your SIP trunk?

If not, then the provider will automatically clip any numbers, not belonging to your number range and set the default number.

Ask your provider, if it is activated and if not, you have to "order" it.

Maybe you could also share the logs of such a call (debug ccsip messages)

[TONY SMITH]

---

@BalSun wrote:

I would like the receiver who has enabled call fwd to the mobile phones to see the actual caller id but i want the outgoing calls to show 1803 at the receiving end. This is an aged care facility and the inmates change often, we do not want the previous inmates friends or relatives calling the room directly while the inmate has been shifted to other room or moved out. 

---

Can you clarify that part?  The person who has enabled call forward won't see the call at all, as it has been forwarded.  What do you want the final called party to see, the original calling number, the number that was redirected, or this default 1803 number?

[BalSun]

Sorry if my writing has confused you. I would like the employees who have fwd the calls to their mobile phones to see the original caller id and not the 1803 number.

In the mean time I ran some tests, here are my observations.

I configured a new number(1880) on cme and enabled call fwd to my personal mobile phone(04xxxx5501).

When i rang 1880 from my work phone (04xxxx3333) the call was forwarded to my personal mobile and i received the correct extension i.e 04xxxx3333. but,

When I called 1880 again from work phone the id was 1803 and all the subsequent calls from the same number was seen as 1803. 

1st time - 3333 --> 1880 --> 5501 (ext seen - 3333)

2nd . . . :  3333 --> 1800 --> 5501 (ext seen - 1803)

[TONY SMITH]

Assuming your PSTN provision is SIP could you post up debugs ("debug ccsip mess") for three calls ..

(1) Normal outgoing call

(2) Call from internal phone to extension with call forward, one of the calls where the final party sees the correct calling number

(3) External call to redirected extension, one where the final party sees the wrong calling number

For (3) could you also note the original calling number?

[BalSun]

Hi Tony,

Please find the log for number (3).

Call flow:

ext mobile(8105) to deskphone(1833) which gets diverted to ext mobile(0484). i will try to get the logs for other two soon. Could not attach the txt file so pasting the logs below.

000729: Feb 21 14:06:36.421: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:xxxxx1833@xx.xx.xx.241:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKdl41n7202gvupmeokus0.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161022 INVITE
Contact: <sip:xxxxx8105@xx.xx.xx.167:5060;transport=udp>
P-Early-Media: supported
Supported: 100rel
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Recv-Info: x-broadworks-client-session-info
Accept: application/media_control+xml,application/sdp,multipart/mixed
P-Visited-Network-ID: cims.corp.ISP.com
X-Codec-Trans-Policy: _AMRNB_AMRWB_EVS_
Session-ID: 35b192a565f727461795fe0e33a2d796
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 753

v=0
o=BroadWorks 2237558420 1 IN IP4 xx.xx.xx.167
s=-
c=IN IP4 xx.xx.xx.167
t=0 0
a=sendrecv
m=audio 18484 RTP/AVP 104 110 9 102 108 8 0 18 105 100
b=AS:128
a=rtpmap:104 AMR-WB/16000
a=fmtp:104 mode-set=0,1,2; mode-change-capability=2
a=rtpmap:110 AMR-WB/16000
a=fmtp:110 octet-align=1; mode-set=0,1,2; mode-change-capability=2
a=rtpmap:9 G722/8000
a=rtpmap:102 AMR/8000

a=fmtp:102 mode-set=7; mode-change-capability=2
a=rtpmap:108 AMR/8000
a=fmtp:108 octet-align=1; mode-set=7; mode-change-capability=2
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 telephone-event/16000
a=fmtp:105 0-15
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=ptime:20
a=maxptime:40
a=sendrecv

000730: Feb 21 14:06:36.437: //196187/1D7CC5A5A5BD/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKdl41n7202gvupmeokus0.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161022 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.6.3.M6a
Session-ID: 00000000000000000000000000000000;remote=3db001ad186257698cfb0c5011b46e11
Content-Length: 0

000731: Feb 21 14:06:36.457: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0000000484@xyz.org.au:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355871D75
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0494836253-2449084908-2780998454-0360545613
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M6a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1645412796
Contact: <sip:xxxxxx8105@xx.xx.xx.241:5060>
Diversion: <sip:xxxxx1803@xyz.org.au>;privacy=off;reason=unconditional;counter=1;screen=no
Expires: 300
Allow-Events: telephone-event
Max-Forwards: 68
P-Asserted-Identity: <sip:NxxxxxxxR@xyz.org.au>
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Type: application/sdp

Content-Disposition: session;handling=required
Content-Length: 321

v=0
o=CiscoSystemsSIP-GW-UserAgent 2822 3243 IN IP4 xx.xx.xx.241
s=SIP Call
c=IN IP4 xx.xx.xx.241
t=0 0
m=audio 17196 RTP/AVP 8 0 18 105
c=IN IP4 xx.xx.xx.241
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 telephone-event/8000
a=fmtp:105 0-15
a=ptime:20

000732: Feb 21 14:06:36.465: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355871D75
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
CSeq: 101 INVITE
Timestamp: 1645412796

000733: Feb 21 14:06:36.497: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355871D75
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>;tag=503863032-1645412796489
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
CSeq: 101 INVITE
Timestamp: 1645412796
WWW-Authenticate: DIGEST realm="xyz.org.au",qop="auth",nonce="BroadWorksXkzw4an9lTnacgx8BW",algorithm=MD5
Content-Length: 0

000734: Feb 21 14:06:36.501: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0000000484@xyz.org.au:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355871D75
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>;tag=503863032-1645412796489
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event

Session-ID: ;remote=
Content-Length: 0

000735: Feb 21 14:06:36.501: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0000000484@xyz.org.au:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355882548
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0494836253-2449084908-2780998454-0360545613
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M6a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1645412796
Contact: <sip:xxxxxx8105@xx.xx.xx.241:5060>
Diversion: <sip:xxxxx1803@xyz.org.au>;privacy=off;reason=unconditional;counter=1;screen=no
Expires: 300
Allow-Events: telephone-event
Authorization: Digest username="NxxxxxxxR",realm="xyz.org.au",uri="sip:0000000484@xyz.org.au:5060",response="4d62571d236cd2c0605326a1eb14e79c",nonce="BroadWorksXkzw4an9lTnacgx8BW",cnonce="F1D45529",qop=auth,algorithm=MD5,nc=00000001
Max-Forwards: 68
P-Asserted-Identity: <sip:NxxxxxxxR@xyz.org.au>
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 321

v=0
o=CiscoSystemsSIP-GW-UserAgent 2822 3243 IN IP4 xx.xx.xx.241
s=SIP Call
c=IN IP4 xx.xx.xx.241
t=0 0
m=audio 17196 RTP/AVP 8 0 18 105
c=IN IP4 xx.xx.xx.241
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 telephone-event/8000
a=fmtp:105 0-15
a=ptime:20

000736: Feb 21 14:06:36.509: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355882548
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>

Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
CSeq: 102 INVITE
Timestamp: 1645412796

000737: Feb 21 14:06:37.749: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355882548
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>;tag=997467003-1645412797739
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
CSeq: 102 INVITE
Timestamp: 1645412796
Supported:
Contact: <sip:0000000484@xx.xx.xx.167:5060;transport=udp>
Privacy: id
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Length: 0

000738: Feb 21 14:06:37.749: //196187/1D7CC5A5A5BD/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKdl41n7202gvupmeokus0.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>;tag=EA527388-1946
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161022 INVITE
Require: 100rel
RSeq: 1340
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:0000000484@xx.xx.xx.241>
Contact: <sip:xxxxx1833@xx.xx.xx.241:5060>
Server: Cisco-SIPGateway/IOS-15.6.3.M6a
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Length: 0

000739: Feb 21 14:06:37.917: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:xxxxx1833@xx.xx.xx.241:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKjiff1s30ao42545ifc40.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>;tag=EA527388-1946
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161023 PRACK
RAck: 1340 220161022 INVITE
Session-ID: 35b192a565f727461795fe0e33a2d796
Max-Forwards: 69

Content-Length: 0

000740: Feb 21 14:06:37.917: //196187/1D7CC5A5A5BD/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKjiff1s30ao42545ifc40.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>;tag=EA527388-1946
Date: Mon, 21 Feb 2022 03:06:37 GMT
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
Server: Cisco-SIPGateway/IOS-15.6.3.M6a
CSeq: 220161023 PRACK
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Length: 0

000741: Feb 21 14:06:42.725: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK355882548
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>;tag=997467003-1645412797739
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
CSeq: 102 INVITE
Timestamp: 1645412796
Supported:
Contact: <sip:0000000484@xx.xx.xx.167:5060;transport=udp>
Privacy: id
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: application/media_control+xml,application/sdp
P-Visited-Network-ID: cims.corp.ISP.com
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Length: 251

v=0
o=BroadWorks 3856555670 1 IN IP4 xx.xx.xx.167
s=-
c=IN IP4 xx.xx.xx.167
t=0 0
a=sendrecv
m=audio 18686 RTP/AVP 8 105
b=AS:128
a=rtpmap:8 PCMA/8000
a=rtpmap:105 telephone-event/8000
a=fmtp:105 0-15
a=ptime:20
a=maxptime:40
a=sendrecv

000742: Feb 21 14:06:42.729: //196188/1D7E9A1DA5C2/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0000000484@xx.xx.xx.167:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.241:5060;branch=z9hG4bK35589E16
From: <sip:xxxxxx8105@xyz.org.au>;tag=EA526E7C-18FC
To: <sip:0000000484@xyz.org.au>;tag=997467003-1645412797739
Date: Mon, 21 Feb 2022 03:06:36 GMT
Call-ID: 1D7E9A1D-xxxxx-A5C6AB36-157D7D4D@xx.xx.xx.241
Max-Forwards: 70
CSeq: 102 ACK
Authorization: Digest username="NxxxxxxxR",realm="xyz.org.au",uri="sip:0000000484@xyz.org.au:5060",response="4d62571d236cd2c0605326a1eb14e79c",nonce="BroadWorksXkzw4an9lTnacgx8BW",cnonce="F1D45529",qop=auth,algorithm=MD5,nc=00000001
Allow-Events: telephone-event
Content-Length: 0

000743: Feb 21 14:06:42.733: //196187/1D7CC5A5A5BD/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKdl41n7202gvupmeokus0.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>;tag=EA527388-1946
Date: Mon, 21 Feb 2022 03:06:37 GMT
Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161022 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:0000000484@xx.xx.xx.241>
Contact: <sip:xxxxx1833@xx.xx.xx.241:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.6.3.M6a
Session-ID: 3db001ad186257698cfb0c5011b46e11;remote=00000000000000000000000000000000
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 6323 8561 IN IP4 xx.xx.xx.241
s=SIP Call
c=IN IP4 xx.xx.xx.241
t=0 0
m=audio 17184 RTP/AVP 8 105
c=IN IP4 xx.xx.xx.241
a=rtpmap:8 PCMA/8000
a=rtpmap:105 telephone-event/8000
a=fmtp:105 0-15
a=ptime:20

000744: Feb 21 14:06:43.045: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:xxxxx1833@xx.xx.xx.241:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xx.167:5060;branch=z9hG4bKm7afu730co2chfe41ds0.1
From: <sip:xxxxx8105@xx.xx.xx.190;user=phone>;tag=405098844-1645412796410-
To: "xxxxx1833 xxxxx1833"<sip:xxxxx1833@xyz.org.au>;tag=EA527388-1946

Call-ID: BW140636410210222-1612367076@xx.xx.xx.190
CSeq: 220161022 ACK
Contact: <sip:xxxxx8105@xx.xx.xx.167:5060;transport=udp>
Session-ID: 35b192a565f727461795fe0e33a2d796
Max-Forwards: 69
Content-Length: 0

[TONY SMITH]

Probably only need the second scenario.  Anyway in your debug there is no Diversion header so your SIP profile has nothing to modify.  That's a shame because it would be relatively easy to try.  The bad news is the ITSPs are inconsistent in how they handle redirected calls, or indeed any call where the calling number isn't within the inbound DDI range.  Just off the top of my head I have dealt with one where the trunk ID was added into one of the headers (contact maybe?), and with that correct you could present any calling number and it would be passed on.  Another one you need them to enable an option in their service, one used the diversion header, and one used PAI.

Any chance of getting some documentation from the ITSP about how they handle redirects?  Unfortunately I don't have an installation Australia that I can look at for ideas at the moment.

Aside from that, if anyone knows how to enable Diversion header in CME then we could try that route.