Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CS1000 not supporting SIP REFER

Status
Not open for further replies.

SherWat

Technical User
Feb 12, 2016
216
0
16
CA
Transferred calls from SIP Line are disconnecting after 15 seconds and I believe it is because the CS1000 doesn't support SIP REFER.
I do not know how to fix this nor where to look.
Anyone have a thought?
 
I found this old records below.

CS1000E rls 5.50
SIP trunks connect to an Avaya ICP IVR system
SIP route data block has TRO YES and VDCH has RCAP TAT

Incoming pstn call routed to the IVR then transferred back to the CS1000 using SIP REFER. Two SIP trunks are held up for the duration of the call - no optimisation takes place.

Declared to be a design limitatiion by Avaya:

'TRO/TAT are MCDN features and currently only supported between two CS 1K nodes that understand the tunnelled MCDN messages on SIP. This feature does not work with any other nortel (including ICP) or third party nodes that do not understand MCDN (Note that the media while using SIP IP peer is always optimized ).'

'TRO feature doesn't work with any 3rd party switch (including Nortel IVR [MPS/ICP]), It works with switches which understands proprietary messages from/to M1/CS1K.

In a nut shell, CS1K does not support SIP trunk optimization with any third party that transfers the call back to CS 1000 using REFER. '

###################################################################

CS1000E rls 5.50
SIP trunks connect to an Avaya ICP IVR system
SIP route data block has TRO YES and VDCH has RCAP TAT

Incoming pstn call routed to the IVR then transferred back to the CS1000 using SIP REFER. Two SIP trunks are held up for the duration of the call - no optimisation takes place.

Declared to be a design limitatiion by Avaya:

'TRO/TAT are MCDN features and currently only supported between two CS 1K nodes that understand the tunnelled MCDN messages on SIP. This feature does not work with any other nortel (including ICP) or third party nodes that do not understand MCDN (Note that the media while using SIP IP peer is always optimized ).'

'TRO feature doesn't work with any 3rd party switch (including Nortel IVR [MPS/ICP]), It works with switches which understands proprietary messages from/to M1/CS1K.

In a nut shell, CS1K does not support SIP trunk optimization with any third party that transfers the call back to CS 1000 using REFER. '

###################################################




Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Another one we used to do when we had Cisco PSTN Gateways SIP into CS1000 was disable the SIP Options as that affected transfer etc.

For 7.5 was the following command on SS to turn off OPTIONS on CS1K:

$ vxShell vtrk sipNpmAppDebugSet tSSG optionSupport 0

If SS is SYSLOADED or even if VTRK application is restarted the setting will be reset, i.e. OPTIONS support will be turned on. To turn it back on same command with a 1 at the end.

But as Firebird said if you have TRO enabled that would be a likely candidate.
 
Changed TRO on route to NO. Did a test call transfer, disconnected after 15 seconds.
Removed TAT in VDCH RCAP. Tried to do a test call transfer, but call wouldn't transfer. Just fast busy.
ADAN DCH 21
CTYP DCIP
DES siptrk
USR ISLD
ISLM 4000
SSRC 3700
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 35
RCAP ND2 MWI TAT
MBGA NO
H323
OVLR NO
OVLS NO
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top