Conference Phone not Reaching Carrier Long Distance Code Entry

[CrzyGK_imported]

I've been working on this issue for some time and any help would be greatly appreciated...

I have a SoundStation IP 6000 connected to an IP Office with a Windstream PRI. I also use a third-part conferencing service that is a long-distance number. When I call that number from any other phone, the call connects and the phone receives a long tone from the provider where they enter their long-distance access code, then the call completes with the conference number.

When I call that same number from the SoundStation, I do not receive the long tone to enter access-code, instead I receive a message from the carrier that my call cannot be completed as dialed. According to the IP Office, both calls send the same digits out of the same PRI and both end in a state "Connected" with Windstream. The only difference that I can find in the Monitor Trace is the failed call ends shortly after it's connected.

I feel like I'm really grasping for straws here, but does anyone know of any data or anything that the SoundStation might be sending that's making it's way to Windstream and wouldn't be very visible in the IP Office?

 

[rdoubrava]

Version of IP Office?
500 or SE ?

 

[CrzyGK_imported]

500 v2 running 9.1

 

[budbyrd]

IP 6000 is a SIP end point that does enblock dialing if I am not mistaken. You probably need a user short code that has the access code written in with the Y character.

Y - Wait for Call Progress Message Wait for a Call Progress or Call Proceeding message before sending any following digits as DTMF. For example, the Y character would be necessary at a site where they have signed up with their telephone service provider to withhold international dialing until a DTMF pin/account number is entered that initiates the call progress/proceeding message.

But I don't have the stuff here to test the theory. I am just guessing.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[CrzyGK_imported]

Just in case this is useful for anyone else, here is what I found. I contacted Windstream and was able to narrow down the issue to a timer for the duration of the long-distance access tone. They were able to adjust it to a slightly longer value and we were able to reach the long-distance tone and enter the code.