If your assessment is correct about the calling number, the carrier will see the original or outside caller's phone number in the From field and reject your call. I see this being solved most of the time with a SIP Profile on the outgoing dial-peer, which adds either a Diversion header or a P-Asserted-Identity header.
E.g., https://community.cisco.com/t5/collaboration-voice-and-video/configure-and-troubleshoot-call-forward-to-the-pstn-using-sip/ta-p/3118287 On Wed, Jul 29, 2020 at 6:45 AM f...@browardcommunications.com < f...@browardcommunications.com> wrote: > > Greetings all, this might be simple fix, I just haven’t dealt with this in > a while. > > We have a unity AA that, when external callers call, select menu options, > etc. Unity will send the call back to. CtiRp, which then CFA to an external > number. You hear the Unity transfer message, 1 second of MoH, then 10 > seconds of nothing, then the call drops. > > Internal calls to the CFA ctirp works > > Internal calls to the unity ctirp then back to the CFA ctirp works. > > I tried having unity call the pstn number directly with same results > > I think the issue is with the calling number is why the carrier is sending > the 603, but it is next to impossible to get them to tell us that. > > Call flow: > Pstn>sipt>cucm >unity>cucm>ctirp-CFA-pstn > > Where would I change the calling number being CFA’ed from Unity to the > PSTN? > > Any ideas? > > Thank you. > > /FW > > Sent from my iPhone > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
