SRG PRI

[someguy758]

I have an issue allowing dialing out through the SRG PRI from redirected set on CS1000e. When i dial a trace show that the call is going out through the ip trunk the right set digits are being inserted for ZDP, entries are there in NRS for the SRG node but all i get is fast busy. SIPCallTrace on SS show incoming message of "404 Not Found". SPN used for ZDP is set as destination code on SRG, remote access packages set.

Any help would be appreciated.

 

[56BelAir]

on the BCM monitor do you see the call coming into the SRG?

 

[someguy758]

BCM monitor does not show any line calls

 

[Dasheen]

I've only worked w/ H323 but did u build a route on the SRG to dial out on the PRI?
U need to assign a separate destination code for the PRI route.

 

[someguy758]

Did build the route, can use the same route when the phone is in local mode.

 

[56BelAir]

Ive got it to work something like this several time
Example only
CS1000 - Zone 120, site ID 120 phones registered on SRG
CS1000- LD 90 SPN 120 RLI 120
CS1000- LD 86 RLI 120 entry 0 route ? SIP to SRG
SRG- VOIP trunks and PRI in remote access package
SRG- trunk access code 120 to use PRI route

 

[56BelAir]

You are hung up in the CS1000 or you would be seeing the call come accross with site ID + digits.
Check your SPN programing as it should be sending the call back down the VOIP trunks.

 

[someguy758]

A trace does show the call hitting one of the IP Trunks on the CS1000 but not on the SRG.

 

[56BelAir]

it seems it may be hungup in NRS you should have site codes built (ie..120 to the srg endoint.

 

[someguy758]

Have that. I am using Zone based digit manipulation and i did change the CTYP entry to SPN and incoming message from SIPCallTrace change to "302 Moved Temporarily". Any suggestions on that and SIP URI Phone context.

 

[someguy758]

I cannot figure this out, calls do not appear to be reaching the SRG according to BCM monitor or could it be that it is getting and SRG does not know how to handle the calls?
Is there anything in particular i need to configure on the SRG to handle these calls when they come in?

 

[Dasheen]

Since bcm monitor doesn't show the call hitting the BCM, problem points back to the CS1k.

On the SRG side did u assign the remote access pkg so the voip trunk can tandem onto the pri trunk to make out bound calls?

 

[56BelAir]

Take it one step at a time
calls should be leaving the cs1000 on your VOIP route, if you trace the call you should read out something like (12018005551212)the 120 representing your site ID.
Once youve got that down the BCM monitor should be seeing the same digits on the BCM VOIP trunks.

 

[biv343]

When you're using SIP, the BCM monitor won't show the lines going active on call setup like the H.323 lines do as all the signalling is out of band, as opposed to in band signalling with H.323. Once the call has terminated, then you'll see the VOIP trunk go into an active state. I'd turn on the MCDN over IP debugging in the BCM monitor UIP tab and see if the calls are making it to the SRG. As long as the remote access package is configured and applied to the IP trunks/PRI lines as dasheen mentioned, and you have a destination code built that absorbs your ZDP and passes the remaining digits to the PRI, then you should be fine.

 

[SupportDude]

These are tough problems for sure.
I would recommend trying the following.
1) Do a routing test in the NRS. Make sure the call type and digits route to the proper endpoint.
2) Verify that your URI tables are identical.

Based on the "404" error it would appear that the NRS can't find the SRG for that particular call.

Everything has to match up. URI table, Codecs, SIP domain, payload sizes, and voice activity detection.


-SD-

http://www.mysupportguy.net

 

[someguy758]

Thanks for the help guys, got it working. Based on what was said here and some reading i decided to start over and now it works. Not to sure what exactly the problem was, did not copy old config for comparison.