VOIP Calls go straight to VM

[Maverick8673]

I need the assistance of the experts so I am coming here first. I am reliving a subject with Call Pilot, BCM, and VOIP... Several months ago I postes that my internal calls to a remote site were ringing right to vm, I turned off VM and the turned it back on that cleared the problem for a month or so, now its back...Calling internal to one remote site sends all calls to VM but calling external and getting transfered is working fine. Any help or suggestions would be greatly appriciated.

 

[Maverick8673]

failed calls orginate from both systems and the software used to be 3.0 but i upgraded to 3.6 to see if that would solve this odd problem. Please lend me the insight as to the document you are refering and let me read LOL

 

[biv343]

First thing I would check (long shot, I know) would be to check your target lines and make sure that the received digits are entered in the private field under the line. When upgrading from 3.0 to 3.6, the received digits will remain in the public field. Since these calls are originating on a private route, it sounds like some quirky MCDN thing happening - the call is tagged as private, but there are no private digits to match to.

Longshot I know, but it's all I can think of off the top of my head.

 

[3Sixty]

Hi Maverick

Have you tried using the BCM monitor and see what number is being presented to the system.

Marshall

 

[3Sixty]

Just another question Maverick have you got 3.0 and 3.6 in the same network. Nothing to do with the fault but there is a patch for interop problems with BCM 3.0 and 3.6

Marshall

 

[Maverick8673]

No, have not tried that monitor where is that located? looking into what you mentioned biv.

 

[3Sixty]

You will find on the main screen install clients. Down near the bottom you should find bcm monitor.

Marshall

 

[3Sixty]

with regards to what Biv suggested I would have said it would depend on how you have configured the route.If you have leading digit 2 in the IP trunk. Then under destination digits 2 or whatever under you programming for the route you will find the dn type options to set the route up as private public etc.

Marshall

 

[jdavid99]

make sure you don't have redirect DN checked and you do have enable network transfers checked.

 

[Maverick8673]

Jdavid, neither were checked.

 

[Maverick8673]

Here is one phone call from the manager log when it hit VM i disconnected the call


06/22/05
Trunk 1 08:50:58 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:58 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:58 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:58 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:58 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:50:59 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:51:00 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:51:00 < CC > CRef Origin: CRef 83 ALERTING
Channel identification - B-B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: std defined for n/w present on n/w side of I/F
0F 00 E9 A0 83 00 01 00 01
Trunk 1 08:51:01 < CC > CRef Origin: CRef 83 NOTIFY
Notification indicator
Notification Description: Unknown/Reserved Value
01 00 F1
Redirecting number - Private/CDP - 7079
Numbering Plan Identification: Unknown/Reserved Value
Type of Number: Coordinated Dialing Plan number
Screening indicator: User provided, not screened
Reason for Redirection: Unknown
Number Digits: - 7079
0F 00 62 00 80 00 04 00 07 0A 07 09
Redirection number - Private/CDP - 7079
0F 00 62 00 80 00 04 00 07 0A 07 09
Trunk 1 08:51:02 < CC > CRef Origin: CRef 83 CONNECT
Connected party number - Private/CDP - 7079
Numbering Plan Identification: Unknown/Reserved Value
Type of Number: ESN CDP
Number Digits: - 7079
05 00 E2 00 04 00 07 0A 07 09
Trunk 1 08:51:07 < CC > CRef Origin: CRef 83 DISCONNECT
Cause - Normal
Location: User
Coding Standard: CCITT standardized coding as described below
Cause Class: Normal Event
Cause: Normal clearing
05 00 80 00 10 00

 

[biv343]

The reason for redirection "unknown" is interesting - you should see call forward no reply (or something to that effect).

7079 is the voicemail DN I'm assuming?

Is voicemail local to this BCM or centralized on the Option 11 Callpilot?

 

[Maverick8673]

VM is local to the BCM and yes 7079 is the VM DN

 

[biv343]

I'm going to throw out one more SWAG here (silly wild a$$ guess).

Check the following:
Target line - prime set for TL is configured as the DN that the line is assigned to.
Target line is assigned to the phone, whether as RO or A/R.

If the above agree (sounds like it will by scanning the above replies), then check one last thing.

Do you use any ringing services (feature 871 if manual, or possibly automatic). If so, check the line assignments in the ring groups - ring group 1 is the default assignment for all lines. If for some reason a ringing service is active, and ring group 1 includes the DN of the voicemail, you could send calls automatically to voicemail. If you do use ringing services, go under the schedule for the ring group, find the target line(s) in question, and set those line to use a ring group that doesn't have a set assigned to it.

Should that not be the case, I will have to plead "stumped".

 

[phones1]

You can use the opt 11 to trace calls and see what dgts/ info is being fed to your bcm, i read earlier about rec dgts in the private field this shouldn't be affect you unless DIA line type is set to private instead of public, also what lev of sware is the OPT11 & ver of ITG. One question do all of your network calls pass through head office.

 

[3Sixty]

Just a quick question

Is this a trace from the BCM monitor?

If so I thought it was VOIP not PRI this seems to indicate that the incoming call is on a PRI interface.

Marshall

 

[biv343]

I thought the same thing - but it will show interface type of PRI even on an IP trunk call.

Had to connect up to my lab system to verify that - never noticed that before.

 

[3Sixty]

Never noticied that before either.

Marshall

Can you put the extension in a pickup group and try a feature 75 from another extension when you see the alerting parameter on the monitor. Just curious what it says on the screen when you pickup the call.

It seems to ring a long time before the voicemail kicks in.

How do you ring from site to site?

Do you just ring extension number or have you an access code to pick up the VOIP lines.

Sorry if I have already asked this

Did you set up the Meridian?

How is the Meridian setup?

 

[Maverick8673]

I noticed that accroding to the monitor its ringing but the user is not hearing or seeing the ring, its seemingling going right to VM, this is the case from BCM to BCM and Meridian to BCM at that one location only, no other location is experieincing this problem. I will try what you have suggested mrmarshall. they are remote to me this could be tricky, my next post will hopefully have the output you need...


Thanks

 

[Maverick8673]

doing the test pick up wont work, being off site doesnt help that...

 

[Maverick8673]

oh and its just extention numbers no pick up groups or anything, the calls originate from one extention calling another 4 digit extention.