SRG call forward issue. Anyone seen this yet?

[tnphoneman]

I have a SRG50 with a PRI. CS1000E at the main office. All sets are registered and working properly with one exception. BCM is all patched up.

SRG is 3.0 and PBX is 5.0 sip trunks.

ext 51xx in normal mode forwards set to CallPilot.
Call comes in PRI at SRG and then you get a message from the CO that the they are unable to complete the call at this time.

Forwarding to any other set on the system works fine. It only fails when forwarding to CallPilot. Ring no answer to CallPilot is fine. Both lines busy you get the same failure as Forward.

I can see the redirect message on the dchannel for the sip trunks and then I also see it on the PRI. I am thinking that is the problem and Nortel will have to fix.

Any suggestions on where to look. We have tried turning off TAT and TRO.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[pronei]

Just curious, are you able to dial the callpilot cdn from a set on the SRG?

 

[tnphoneman]

Yes and RNA works fine.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[pronei]

Well, its sounds like a trunk to trunk transfer issue, if your getting a message from the CO, put a ticket in with the telco and have them the call and see exactly whats going on.

Perhaps the PRI isn't provisioned completely correct.

 

[tnphoneman]

What gets me is that on a transfer to another set the BCM does not send a redirect notification to the CO but when you send the call to the CallPilot it does.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[strmwalker]

tnphoneman...what type of callpilot server are we talking
about?

no problems only solutions

strmwalker

 

[pronei]

Error in my previous post,

Have the CO TRACE the call to see whats going on.

 

[tnphoneman]

1005 on 5.0.

Working with Nortel and they think it may be that I need a beta patch. Will know shortly.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[allenmac]

Check the Route Data Block for the SIP route. I have seen NCRD = YES cause issues like this. The carrier sometimes freaks out if they get these messages.

 

[tnphoneman]

Good suggestion but that does not do it.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[tnphoneman]

Keep an eye out. There will be a patch for the SRG coming out probably next week with the fix for this one.


Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.