INFO

How to use SwyxConnect 172x with SwyxWare 2013 (R2) (kb4492)

The information in this article applies to:

  • SwyxWare 2013 R2
  • SwyxWare 2013
  • SwyxConnect 1724
  • SwyxConnect 1723
  • SwyxConnect 1722

[ Information ]


Information

The following configuration settings are required to successfully use SwyxConnect 172x with SwyxWare 2013 oder 2013 R2:

  • If SwyxConnect 172x is used as 3rd party SIP gateway, or 3rd party SIP devices, ISDN phones or analog devices are registered via SIP at SwyxServer, you need to configure the following registry key:
    Path: HKLM\Software\[Wow6432Node\]Swyx\IpPbxSrv\CurrentVersion\Options
    Name: AllowReRegisterWithAlteredCallId
    Type: REG_DWORD
    Value: 1

    Background information: SwyxConnect 172x creates for each SIP reregistration a new SIP Call-ID. SwyxWare 2013 follows more exact the RFC 3261 definitions to differentiate between new registrations and reregistrations. With the above mentioned key SwyxWare 2013 acts more tolerant regarding this issue.
     
  • If the above mentioned devices are registered via SwyxConnect 172x at a SwyxServer 2013 and you want to use the transfer functionality, then you need to add the following registry key:

    Path: HKLM\Software\[Wow6432Node\]Swyx\IpPbxSrv\CurrentVersion\Options
    Name: SIPTransferIdMode
    Type: REG_DWORD
    Value: 0

    Background information: SwyxWare 2013 uses the message headers defined in RFC 3515 for SIP REFER requests. SwyxConnect 172x does not fully comply to this standard. Via the registry key you can switch to an alternative method.

Hint: Both registry keys will change the SwyxServer behavior globally! Please use these keys only, if SwyxConnect 172x and the above mentioned scenarios are in use.


Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.