CM concurrent call forwarding limit?

[Jakubowski]

I have an older CM, and I'm moving to a new phone system, and in the mean time, I've been forwarding calls from the existing CM to the new phone system. All the sudden I'm getting calls that aren't going through.

Call comes in to PRI on the G450 PRI line card, gets forwarded to an outside DID on my new phone system. This is inefficient and uses 2 lines on my PRIs, but I don't have that many calls. Using Monitor Traffic Trunk, I'm seeing less than a dozen in use. Trunk group 10 are my 2 PRIs, looks like this as of now, highest number I've seen since I started looking at this is 12.

S A Q W # S A Q W # S A Q W
10 46 2 0 0
(#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting)

When a call fails, the caller gets a recording like "extension 1234 busy, please wait." then the call ends. Extension 1234 is my attendant station, since unplugged, it's physically in a box someplace.

So I'm assuming here I'm hitting some sort of call forwarding limit, and it's sending the calls to the attendant instead, but I don't know why. I'm even seeing the issue now when most people went home, where my monitor traffic trunk shows 2 active lines out of 46.

Any suggestions?

 

[avayaguy23]

How are you forwarding calls? Off-Pbx, xmobile etc.

 

[Jakubowski]

The old system has a DID for every handset, so I just go into that station, and change all the Enhanced Call Forwarding to active and give it the DID of my new system.

The odd part here is this has worked for months, but now seems to work horribly.

 

[avayaguy23]

I would suggest posting a trace of the calling failing. You probably need to trace the trunk tac and also the extension. Depends on where the issue is at.

 

[Jakubowski]

That's the odd thing, tracing either the station or the trunk, I don't even see the 2nd call. The first call is my desk phone, which is off-net, so I'm calling the way a normal end-user would call. I'm 518-377-1234. Calls should be forwarded from ext 5499 to the 518-912345 number. Obviously I've obfuscated the numbers


Trace the extension:


16:57:20 TRACE STARTED 01/04/2021 CM Release String cold-02.0.823.0-21388
16:57:28 Calling party trunk-group 10 member 1 cid 0x1edc
16:57:28 Calling Number & Name 5183771234
16:57:28 term station 5499 cid 0x1edc
16:57:28 call-forwarding 9518912345
16:57:28 term trunk-group 10 cid 0x1edc
16:57:28 dial 95189512345 route:HNPA|ARS
16:57:28 route-pattern 5 preference 1 location ALL cid 0x1edc
16:57:28 seize trunk-group 10 member 23 cid 0x1edc
16:57:28 Setup digits 9518912345
16:57:28 Calling Number & Name 5183771234 NO-CPName
16:57:29 Proceed trunk-group 10 member 23 cid 0x1edc
16:57:30 active trunk-group 10 member 23 cid 0x1edc
16:57:57 idle trunk-group 10 member 1 cid 0x1edc
16:57:59 Calling party trunk-group 10 member 2 cid 0x1ede
16:57:59 Calling Number & Name NO-CPNumber NO-CPName
16:57:59 idle trunk-group 99 member 21 cid 0x1ede

Trace the trunk:

17:02:00 TRACE STARTED 01/04/2021 CM Release String cold-02.0.823.0-21388
17:02:04 Calling party trunk-group 10 member 4 cid 0x1ef0
17:02:04 Calling Number & Name 5183771234 ACTURE SOLUTI
17:02:04 active trunk-group 10 member 4 cid 0x1ef0
17:02:04 dial 5499
17:02:04 term station 5499 cid 0x1ef0
17:02:04 call-forwarding 951891234
17:02:04 term trunk-group 10 cid 0x1ef0
17:02:04 dial 95189123431 route:HNPA|ARS
17:02:04 route-pattern 5 preference 1 location ALL cid 0x1ef0
17:02:04 seize trunk-group 10 member 7 cid 0x1ef0
17:02:04 Setup digits 518951234
17:02:04 Calling Number & Name 5183771234 NO-CPName
17:02:04 Proceed trunk-group 10 member 7 cid 0x1ef0
17:02:05 active trunk-group 10 member 7 cid 0x1ef0
17:02:24 idle trunk-group 10 member 4 cid 0x1ef0

 

[avayaguy23]

You sure that trunk isn't at capacity? Sounds like you are at capacity or you have a loop causing the channels to be at capacity.

 

[Jakubowski]

I'm definitly not a CM expert.
But I run this command: Monitor Traffic Trunk

and the output shows I'm not using even 1/2 my trunks.
All the calls in the logs are using trunk 10, both the incoming and outgoing.

So while it really seems like out of capacity, I just can't see anything that actually shows that.

I'm just not even sure what else to look at, especially since as far as I know, this has worked fine for over a year. My worry now is that it hasn't been working fine, and somehow I've never noteiced.

 

[avayaguy23]

You want to run the command status trunk 10. While this view is not live, it will give you a better perspective.

 

[Jakubowski]

I knew I wasn't doing what I wanted the best way, but it had been working.

But I got some other help

Using the command:
Change inc-call-handling-trmt trunk-group xx

that lets me change the digits, and it seems to work without issue. At the very least I was able to do 3 concurrent calls without issue.

still don't know why the old way just stopped working, but I just needed a solution.

thanks.