Currently have engineers (and myself) scratching heads until they bleed over SIP REFER issue where Avaya SES plays deaf to GVP’s REFER message. 7.2 works, 7.6 doesn’t. 7.2 was a third party SIP stack, 7.6 is Voice Genies’ SIP stack. Doing a compare side by side of the REFER messages, the Genesys message is compliant with RFC 3515 & 3261, though they did toss in some proprietary garbage (a Telera session ID! Telera is ancient history to everyone by Genesys), but SES should ignore that. No errors being thrown by SES, just sits there and the REFER retries die at the proscribed time out with a BYE.
So believe that this is primarily, if not solely Avaya issue, but am interested if anyone else has played with this combination.
Turns out that Genesys ran into the bug back in mid-2008 and it took Support almost two weeks to figure that out. : A hot fix was released in August 2008 that corrected the problem.
Release Number 7.6.200.46 [08/27/08] – Hot Fix
IPCS no longer sends a REFER message containing multiple values in “Referred-by” header. The “Referred-by” header in the REFER message from IPCS will now contain only a single value. Previously, if IPCS received an INVITE with a “History-info” header containing multiple values (separated by commas), the REFER that was sent by IPCS also had “Referred-by” header containing multiple values as received in “History-info” header. (ER# 200037661)
A hot fix was released in August 2008 that corrected the problem.