Referred headers supported in OXE? / Service Unavailable

[DS_Eire]

Hi,

I have an OXE on R10 with IP sets (ip40X8 running NOE). I have an Avaya environment with endpoints and a conference server.

An avaya set dials into a conference and initates a dialout to an OXE set. During this dialout sequence a REFER message is sent by the avaya set to the avaya pbx and this triggers an invite to be sent from the avaya pbx to the OXE set. In the invite message there is a "Referred-By" header - does the OXE handle Refer headers in invites? I don't suspect this is causing an issue but just said I'd throw it out there.

The call fails with server "Service Unavailable" sent by OXE. Attached is a trace of the call. Any ideas?

Thanks

[alex]

It is supported as of RFC 3892

Supported RFC’s in Release 9.0
2543 (obsolete by RFC 3261,3262, 3263,3264, 3265) :SIP (Session Initiation Protocol)
2782: A DNS RR for specifying the location of services (DNS SRV)
2822: Internet Message Format
3261: SIP (Session Initiation Protocol)
3262: Reliability of Provisional Responses in SIP (PRACK)
3263: SIP: Locating SIP Servers
3264: An Offer / Answer model with SDP
3265: SIP-Specific Event Notification
3323: Privacy Mechanism for the Session Initiation Protocol (SIP)
3324: Short term requirements for network asserted identity
3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
3515: The Session Initiation Protocol (SIP) refer method
3891/3892: The Session Initiation Protocol (SIP) 'Replaces' Header/ Referred-By Mechanism
4497: Inter-working between SIP and QSIG

[DS_Eire]

Thanks - is this configurable in OXE or enabled by default?

[alex]

Thanks - is this configurable in OXE or enabled by default?

Enabled by defautl. Just check how call transfer works.