Lucy, Thank you! After communicating with support I realized I had put the setting you suggested in the wrong location in Brekeke. I added the setting in the Advanced configuration in the Sip Server instead of the PBX. Based on the feedback from support I moved the setting to the correct location at ...

Lucy,
I have sent the logs to support.

Thanks,
wfx

Lucy, Thank you for your help! The IVR is not registered as an extension, per your suggestion I added the following to my configuration>Advanced and restarted the PBX, but no change: com.brekeke.pbx.Setting.ALLOW_REFER=true I am still receiving 403 Forbidden, are you sure the syntax is correct? I ...

FYI - Here is a section from the log where the PBX/BSS receives the REFER and then responds with the 403. Address reference: 10.20.20.20 = Interface IP of APP/IVR 10.10.10.10 = Interface IP of PBX/BSS 99.99.99.99 = ITSP IP Address 1111111111 = Original DID of caller 2222222222 = New DID to transfer ...

So I changed the configuration to move the call via the ARS routes and now when the REFER comes from the IVR to the PBX/BSS it responds with a 403 Forbidden. I assume this is because the REFER is requesting a transfer to a number outside of the PBX and the IVR server is not registered as an ...

Never mind, got that figured out, created new ARS route to route calls to the SIP/IVR server that match inbound DID from PSTN.

Still working on it...

wfx

I see what you are thinking and it might work, but I ran into issue trying to configure this. I need the INVITE from the ITSP to go to my external App/IVR, but in the ARS "Patterns-In' route from the ITSP I cannot specify a SIP uri/IP address to forward the call to, only extensions, I think this is ...

The original packet from the IVR has the PBX/BSS IP in it's REFER-TO, but when the PBX/BSS forwards it to the ITSP it changes the REFER-TO to it's own external NAT address. Detail: Address reference: 10.10.10.10 = Interface IP of PBX/BSS 44.44.44.44 = External IP of PBX/BSS (Config/Network/Inteface ...

I use PBX for ARS to authenticate and connect to the ITSP. The IVR signaling cannot be changed. I find it hard to believe the PBX/BSS cannot support replacing the REFER-TO address. Without this feature I don't know how you could proxy a transfer at all. I currently operate this App/IVR on other ...

snuyzm, The INVITE comes from the ITSP. Remember my call flow is like this with calls originating on the PSTN going into the IVR and then being transferred to another location on the PSTN: PSTN(#A)->ITSP->PBX/BSS->IVR ........................................[REFER] PSTN(#B)<-ITSP<-PBX/BSS<-IVR My ...

snuyzm, I don't have B2B-UA enabled in config or in the dial plan rule. Even tried enabling it to see if it made a difference but no luck. By out of the dialog I mean out of the current session/call/conversation etc... My basic call flow is like this: ITSP->PBX/BSS->App/IVR I have dial plan rule for ...

snuyzm, Yesterday I had tried this, to force the message to a destination: Deploy Patterns: $target = 99.99.99.99 When doing this the ITSP get's the REFER, but denies it most likely since it's not in an active dialog. In Wireshark I can see the ITSP respond to the REFER with a 403, but the BSS does ...

snuyzm, I actually figured out the leading "&" in the advanced config was the issue for the rules not executing by cross referencing some other examples of Advanced configurations. I was coming back to post this with an update when I saw your post. Thank you though for the quick reply and solution ...

1. Brekeke Product Name and Version: PBX/Sip Server Advanced 3.7.7.3/477 2. Java version: 1.8.0_144 3. OS type and the version: Windows Server 2012 4. UA (phone), gateway or other hardware/software involved: SIP application, ITSP 5. Your problem: My SIP application issues a REFER to transfer a call ...