Certain incomming PRI calls rejected

[jomaha]

I have a Legend connected to a PC running asterisk via a PRI. Certain calls coming in on a 5ess PRI are being rejected. Here is the setup

telco_PRI -> Asterisk_1 -> Asterisk_2 -> Merlin_Legend_2
...are accepted.

System_75_T1 -> Asterisk_1 -> Asterisk_2 -> Merlin_Legend_2
...are rejected when the System_75 T has no caller ID assigned (and why would it. This is a wink start T). But calls are accepted if I assign a caller ID to the S75 T at Asterisk_1 (but this call causes the bchannels to restart).

Now I have another (Asterisk_3 -> Merlin_Legend_3) setup which does not have this problem. So this tells me that the ML_2 is being more restrictive on the type of ISDN calls it receives. Where would I look to adjust this?

I have Network Services set to CallByCall and Incomming Routing set to DialPlan.

Thanks,

John

 

[jomaha]

One more thing... I had this port configured as a standard T. It may have been a DID. I think I have removed all the old configuration but who knows? Is there a way I can 'wash' all the past configuration for a slot (in this case 5 - and there are cards to the right)?

John

 

[jomaha]

Found out what is happening... longer caller ID name strings are causing the d-channel to reset and drop calls in progress. Does anyone know what the maximum length of this parameter is (for 5ess - and does the Legend match this spec)? There will be a fix for this in Asterisk soon.

 

[jomaha]

I have been meaning to put together some documentation (to post here and the asterisk wiki) on integrating asterisk and the legend over PRI. Got things working pretty nicely. Illuminating message waiting lamps is one of the final hurtles.

John

 

[stroyer74]

John,

Just checking to see if you have had a chance to post any documentation on the Asterisk wiki yet. I am very interested in attempting an integration between my Merlin Magix and Asterisk - figure that it parts should be similar to your Legend system.

I'm sure you have a million things to do besides put together a documentation package, but since you indicated that you might do that, just letting you know that I'm interested.

Thanks,
Sheldon