cclarkson

Hi,

We're currently having problems with path replacement on our S8700. Our current load is -

Operating system: Linux 2.4.20-AV15 i686 i686
Built: Mar 15 09:42 2005
Contains: 02.1.118.1
Reports as: R012x.02.1.118.1
Release String: S8700-012-02.1.118.1
UPDATES:
There are no updates on the system.
Translation Saved: Mar 2 02:01
License Installed: Dec 14 12:24


We currently route some inbound calls over a Qsig trunk to our voice xml app (VoiceGenie). Routing is as follows -

VDN to vector

01 wait-time 1 secs hearing ringback
02 route-to number 7221 with cov y if unconditionally
03 stop

7221 relates to our uniform dial plan table below -

Matching Insert
Pattern Len Del Digits Net Conv
72 4 0 555 aar n

aar table is as follows-

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
555 3 7 5 aar n

Route pattern 5 strips the leading 555 digits and sends the call over our qsig trunk. Calls route succesfully.

Depending on the customers choices within the voice app, the call may have to be transferred to and agent. When the call is transfered to the agent, path replacement should kick in to free up the ports on the VoiceGenie but it never does.

We have played about with the settings on our qsig page and the trunk page and whilst the call always gets to the voicegenie app, path replacement never seems to kick in. Our qsig features at present are as follows -

ISDN PARAMETERS
Send Non-ISDN Trunk Group Name as Connected Name? n
Display Connected Name/Number for ISDN DCS Calls? n
Send ISDN Trunk Group Name on Tandem Calls? n
Send Custom Messages Through QSIG? n
QSIG TSC Extension: 3300
MWI - Number of Digits Per Voice Mail Subscriber: 5
National CPN Prefix: 0
International CPN Prefix: 00
Pass Prefixed CPN to ASAI? n
Unknown Numbers Considered Internal for AUDIX? n
USNI Calling Name for Outgoing Calls? n
Path Replacement with Measurements? y
QSIG Path Replacement Extension: 3005
Path Replace While in Queue/Vectoring? n


We've also had this logged with Avaya and VoiceGenie and got an isdn trace done which just resulted in both of them pointing the finger of blame at each other (which isn't helping, to be honest). So I'm sort of stuck in limbo at the moment!

Has anyone else experienced a path replacement problem similar to this before or am I (and Avaya and VoiceGenie) missing something obvious? Are there perhaps any related patches needed for this? Any help at all would be great...

Thanks for reading, I know it dragged on a bit!

Craig