Any experience with GVP 7.5/7.6 and Avaya Comm Mgr 4.x or 5.x SIP? (SOLVED)

[Gulden_NL]

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.

[Gui75]

Hi Guilden

Could you post 7.2 REFER and 7.5 REFER as taken from logs?

Regards

[Gulden_NL]

Disregard IP addresses, they have been changed to protect the innocent. 

INVITE sip:1138012@bobsouruncle.com SIP/2.0
From: sip:7148620529@bobsouruncle.com:5061;tag=094686c8761ur3ffde483e939h73
To: "1138012" <sip:1138012@bobsouruncle.com>
Call-ID: 094686c8761ur30df483e939h73
CSeq: 1 INVITE
Max-Forwards: 70
Route: <sip:acm-routed@164.21.413.59:5061;lr;phase=endpoint;transport=tls>
Record-Route: <sip:164.21.413.67:5061;lr;transport=tls>
Via: SIP/2.0/TLS 164.21.413.67;branch=z9hG4bK094686c8761ur31df483e939h73
User-Agent: Avaya CM/R014x.00.3.737.4
Supported: 100rel,timer,replaces,join,histinfo
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS
Contact: <sip:7148620529@164.21.413.67:5061;transport=tls>
Session-Expires: 240;refresher=uac
Min-SE: 240
P-Asserted-Identity: sip:7148620529@bobsouruncle.com:5061
Content-Type: application/sdp
History-Info: <sip:1100020@bobsouruncle.com>;index=1
History-Info: "MCI ISDN PRI 1869" <sip:1100020@bobsouruncle.com?Reason=SIP%3Bcause%3D302%3Btext%3D%22Moved%20Temporarily%22&Reason=Redirection%3Bcause%3DNORMAL%3Bavaya-cm-reason%3D%22vector-directory-number%22>;index=1.1
History-Info: "IVR APP #1" <sip:1100105@bobsouruncle.com>;index=1.2
Accept-Contact: *;+avaya-cm-line=1
Alert-Info: <cid:external@bobsouruncle.com>;avaya-cm-alert-type=external
Content-Length: 156

[Gulden_NL]

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)