[HELP] Avaya SBCE - SIPREC triggers on inbound calls but NOT on outbound calls
Platform: Avaya SBCE 10.2.1.3-111-25777
Topology: IPO ↔ SBCE ↔ NT/SIP Trunk, SIPREC Server (192.168.5.8)
Problem
SIPREC works correctly for inbound calls (NT → SBCE → IPO) but never triggers for outbound calls (IPO → SBCE → NT), despite both directions sharing the same EPG, Media Rule, and Recording Profile.
Network Layout
Outbound: IPO → SBCE InternalA1 → NT
Inbound: NT → SBCE ExternalB1 → IPO
Configuration
SIP Server — SIPREC
Routing Profile — TO_SIPREC
Recording Profile — SIPREC
Media Rule — IPO
End Point Policy Group — IPO
Server Flows — SIP Server: SIPREC
PCAP Evidence
✅ Inbound (NT → SBCE → IPO) — SIPREC WORKS
NT (192.168.44.1) → SBCE ExternalB1 INVITE sip:[email protected]
SBCE → SIPREC (5.8) INVITE sip:192.168.5.8:5060 [Require: siprec]
↑ triggered immediately, before call is answered
SBCE → IPO (5.3) INVITE sip:[email protected]:5060
SIPREC → SBCE 100 Trying → 200 OK
SBCE → SIPREC ACK
IPO → SBCE 200 OK (answered)
SBCE → SIPREC UPDATE (metadata updated with called party info)
SIPREC → SBCE 200 OK (UPDATE)
SBCE → SIPREC BYE → 200 OK
❌ Outbound (IPO → SBCE → NT) — SIPREC DOES NOT TRIGGER
IPO (192.168.5.3) → SBCE InternalA1 INVITE sip:[email protected]
SBCE → NT (192.168.44.1) INVITE sip:[email protected]:5060
[NO SIPREC INVITE sent to 192.168.5.8]
NT → SBCE 100 Trying → 180 Ringing → 200 OK
SBCE → IPO 200 OK → ACK
IPO → SBCE BYE → 200 OK
Key Observation
Both flows are configured identically (same EPG, Routing Profile, Signaling Interface). The only difference is the Received Interface.
Question
Has anyone seen SIPREC trigger correctly for one direction but silently fail for the other? Could there be a restriction on SIPREC triggering for calls received on an internal interface (InternalA1)?
Any help appreciated — happy to provide additional logs or screenshots.
Topology: IPO ↔ SBCE ↔ NT/SIP Trunk, SIPREC Server (192.168.5.8)
Problem
SIPREC works correctly for inbound calls (NT → SBCE → IPO) but never triggers for outbound calls (IPO → SBCE → NT), despite both directions sharing the same EPG, Media Rule, and Recording Profile.
Network Layout
| IPO (internal PBX) | 192.168.5.3 | — |
| SBCE — InternalA1 | 192.168.5.5 | A1 |
| SBCE — ExternalB1 | 192.168.44.5 | B1 |
| NT / SIP Trunk | 192.168.44.1 | — |
| SIPREC Server | 192.168.5.8 | same subnet as A1 |
Inbound: NT → SBCE ExternalB1 → IPO
Configuration
SIP Server — SIPREC
- Type: Recording Server | IP: 192.168.5.8:5060 TCP | Heartbeat: UP
Routing Profile — TO_SIPREC
- Next Hop: 192.168.5.8:5060 TCP
Recording Profile — SIPREC
- Routing Profile: TO_SIPREC | Type: Full Time | Terminate on failure: OFF
Media Rule — IPO
- Media Anchoring: ON | Recording Server: ON | Recording Profile: SIPREC | Media Forking: None
End Point Policy Group — IPO
- Media Rule: IPO | Application Rule: default
Server Flows — SIP Server: SIPREC
| 1 | SIPREC | ExternalB1 | InternalA1 | IPO | TO_SIPREC |
| 2 | OB_SIPREC | InternalA1 | InternalA1 | IPO | TO_SIPREC |
PCAP Evidence
✅ Inbound (NT → SBCE → IPO) — SIPREC WORKS
NT (192.168.44.1) → SBCE ExternalB1 INVITE sip:[email protected]
SBCE → SIPREC (5.8) INVITE sip:192.168.5.8:5060 [Require: siprec]
↑ triggered immediately, before call is answered
SBCE → IPO (5.3) INVITE sip:[email protected]:5060
SIPREC → SBCE 100 Trying → 200 OK
SBCE → SIPREC ACK
IPO → SBCE 200 OK (answered)
SBCE → SIPREC UPDATE (metadata updated with called party info)
SIPREC → SBCE 200 OK (UPDATE)
SBCE → SIPREC BYE → 200 OK
SIPREC INVITE body: multipart/mixed with 2 audio streams (label:10, label:20, both sendonly) + rs-metadata XML per RFC 7866.
❌ Outbound (IPO → SBCE → NT) — SIPREC DOES NOT TRIGGER
IPO (192.168.5.3) → SBCE InternalA1 INVITE sip:[email protected]
SBCE → NT (192.168.44.1) INVITE sip:[email protected]:5060
[NO SIPREC INVITE sent to 192.168.5.8]
NT → SBCE 100 Trying → 180 Ringing → 200 OK
SBCE → IPO 200 OK → ACK
IPO → SBCE BYE → 200 OK
Only periodic OPTIONS keepalive is observed between SBCE and 192.168.5.8. No SIPREC signaling at all.
Key Observation
| Inbound (NT→IPO) | ExternalB1 | SIPREC (Pri 1) | ✅ Works |
| Outbound (IPO→NT) | InternalA1 | OB_SIPREC (Pri 2) | ❌ Silent fail |
Question
Has anyone seen SIPREC trigger correctly for one direction but silently fail for the other? Could there be a restriction on SIPREC triggering for calls received on an internal interface (InternalA1)?
Any help appreciated — happy to provide additional logs or screenshots.
