" /> Genesys SIP to a Avaya SES - Genesys CTI User Forum

Author Topic: Genesys SIP to a Avaya SES  (Read 3164 times)

Offline chuck14

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Genesys SIP to a Avaya SES
« on: April 06, 2009, 10:41:55 PM »
Advertisement
Need help in configuring the Genesys SIP and Avaya SES intregration.  we are configuring our Genesys SIP to have an external route point forwading to the avaya ses server.  We can see in the sys logs on both device the request being except by the ses but the call is terminated.  I don't see the call be forwarded to the cm. 

Any suggestions??

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: Genesys SIP to a Avaya SES
« Reply #1 on: April 07, 2009, 01:53:54 AM »
Chuck,

here are the basic things that I would suggest without seeing the log:

1.  in SIP T-Server log, what does it say for response to INVITE
2. is INVITE parameters correct (ip address, dn....)

I would start with checking if I got the access codes right - how are you defining trunk in SIP T-Server and prefixes inside there?

Offline Gulden_NL

  • Full Member
  • ***
  • Posts: 109
  • Karma: 1
    • VoxPeritus - The Voice of Experience
Re: Genesys SIP to a Avaya SES
« Reply #2 on: April 17, 2009, 01:41:50 PM »
Which versions?  I know of a problem with 7.6 Genesys that has been fixed with a hot patch.  I don't have the patch information on this system, but it was released in July 2008 and addresses a problem of adding additional information in the REFER which causes Avaya to drop the call with no information in the Avaya logs.

Here's an example of the offending information:
[i]History-Info: "MCI ISDN PRI 1869" <sip:1100020@genesyslabs.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[/i]