Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Switching a call out of one BCM from another BCM

Status
Not open for further replies.

TLBRINSON

MIS
Jul 1, 2006
17
US
I manage a BCM400 and a BCM50, each in different area codes connected by a T1 data line running VoIP. There is also a PRI line coming into both BCM's. I am atttempting to set it up to where both locations can dial out of each other's PRI to save on long distance charges. On the end that I am at, there is only 1 area code, but on the other end there are 3 that are local. I have it set up to where if you dial an 8 then the area code, it will route and switch out at the other end. One of the area codes is working perfectly, if you dial 8281??????? it works fine, and you can have multiple calls going at once. However, with the 8713 area code, you can only have 1 call at a time. If one person dials a number with 8713???????, it goes thru just fine. If that person is still on the phone, the next person to dial an 8713 number gets a fast busy. Everything is set up identially in the BCM's for the 2 area codes, including the destination codes in the dialing plan and the remote gateways under telephony resources. I would appreciate any ideas. Below is a trace of the call using BCM monitor.

Manvel
Mon Jun 18 09:23:57 2007

[BCM Info]

[BCM Hardware]
[Platform] "BCM50+Eth. Router"
[CPU] "8270 266 MHz"
[Memory] "251 MB"
[Hard drive] "Maxtor 6N040T0"
[Profile] "N/A"
[System ID] "0016CA3EF1EC"
[Serial number] "NNTMHD007CDH"

[BCM Software]
[Version] "1.00.2.04.j"
[Boot time] "6/14/07 7:13 PM"

[IP Configuration]
[Published IP address] "172.16.4.55"
[Next hop] "172.16.4.254"
[Installed Devices] "NIC: eth0"
" IP 10.10.99.1"
" Mask 255.255.255.252"
" MAC 00-16-CA-3E-F1-EC"
"NIC: eth1"
" IP 172.16.4.55"
" Mask 255.255.255.0"
" MAC 00-16-CA-3E-F1-ED"
"NIC: eth2"
" IP 10.10.11.1"
" Mask 255.255.255.252"
" MAC 00-16-CA-3E-F1-EE"
--------------------------------------------------------

[Media Card]

[Media Card Hardware]
[Type] "CSC"
[Revision] "7"
[Voice Bus channels] "N/A"

[Media Card Firmware]
[Core load] "30DfC33 I/7e"
[Market profile] "North America"

[Media Card Configuration]
[DS30 configuration] "N/A"
[Dial-up WAN] "N/A"
[Media channels] "160"
[Signaling channels] "72"
[Processor expansion cards] "N/A"
[DSP resource units] "60"
[DSP Resources]
[Main DSP (20%)]
[Available Tasks: 48 G711 48 G711-V 19 G729 4 Modem 13 Fax 13 T38 160 CMixer 160 CParty 160 CPTD 160 DTMFD 96 GASI 96 GATI ]
[Loaded Tasks (56)]
[Analog Set (4)]
[Conference Mixer (6)]
[Conference Party (18)]
[Data Modem (1)]
[DSP Logger (1)]
[Tone Generator (26)]
--------------------------------------------------------

[Voice Ports]

[Voice CTI Ports]
[Resource limit] "11"
[Enabled ports] "11"
[Assigned ports] "11"
[Active (on call)] "1"

[Call Center]
[Assigned ports] "N/A"
[Active (on call)] "N/A"

[IVR]
[Assigned ports] "N/A"
[Active (on call)] "N/A"

[Voice Mail]
[Assigned ports] "10"
[Active (on call)] "0"
[Voice Port Details]
[Modem - group DN 2364]
[2364 - Standby Modem]
[Voice Mail - group DN 2363]
[2354]
[2355]
[2356]
[2357]
[2358]
[2359]
[2360]
[2361]
[2362]
[2363]
--------------------------------------------------------

[IP Devices]

[IP Clients]
[Used licenses] "1 of 1"

[I20xx Sets]
[Enabled] "1"
[Connected] "1"
[Active (on call)] "0"

[Wireless Sets]
[Enabled] "0"
[Connected] "0"
[Active (on call)] "0"

[IP Trunks]
[Used licenses] "6 of 6"
[Active (on call)] "0"
[MCDN over IP] "Enabled"
[IP Set Details]
[DN: 5022 Type: I2004 IP:port: 172.16.6.62:5000 ]
--------------------------------------------------------

[RTP Sessions]

[Local IP Endpoints]
[IP to IP] "0"
[TDM to IP] "0"
[TDM to TDM] "0"
[Est. bandwidth] "0 bps"

[Local to Remote IP Endpoint]
[IP to IP] "0"
[TDM to IP] "0"
[Est. bandwidth] "0 bps"

[Remote IP Endpoints]
[IP to IP] "0"
[Est. bandwidth] "0 bps"

[Media Gateways]
[Active (on call)] "0 of 2"
[RTP Session Details]
[*Empty*]
--------------------------------------------------------

[UIP]

[UIP Modules]
[MCDN Over IP] "CHECKED"

[Loop]

[1]

[2]

[3]

[4]

[Module 1]
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"

[Module 2]
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"

[Module 3]
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"
"UNCHECKED"

[Logging]
[Log UIP data] "UNCHECKED"
[Universal ISDN Protocol Messages]
[MCDN]
[Trunk 1 09:20:46 > CC < CRef Origin: CRef 22C7 SETUP NAS 9792302913 87134364174]
[Bearer capability - Speech - G.711 u-law]
[Information Transfer Capability: speech]
[Coding Standard: CCITT standardized coding]
[Information Transfer Rate: 64 Kbits/s]
[Transfer Mode: circuit mode]
[User Information L1 Protocol ID: Recommendation G.711 u-law]
[Layer and Protocol Identification: User Information L1 Protocol]
[13 00 81 90 00 00 A2 00 00 00 00 00 00 00 ]
[Channel identification - 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: 0]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : ]
[0F 00 69 00 83 00 01 00 81 00 ]
[NA Facility - NAS]
[0F 00 11 FD 11 00 A1 0F 02 01 01 02 01 A1 30 07 80 05 30 03 81 01 01 09 ]
[Calling party number - E.164/National - 9792302913]
[Numbering Plan Identification: ISDN/Telephony numbering plan (Rec. E.164)]
[Type of Number: National Number]
[Screening indicator: User provided, not screened]
[Presentation indicator: Presentation allowed]
[Number Digits: - 9792302913]
[07 00 21 80 0A 00 09 07 09 02 03 0A 02 09 01 03 ]
[Called party number - Unknown/Unknown - 87134364174]
[Numbering Plan Identification: Unknown]
[Type of Number: Unknown/Reserved Value]
[Number Digits: - 87134364174]
[03 00 80 00 0B 00 08 07 01 03 04 03 06 04 01 07 04 ]
[Trunk 1 09:20:52 < CC > CRef Origin: CRef 4 ALERTING NAS]
[Channel identification - B-Channel 1]
[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: CCITT standard as in Recommendation Q.931]
[Channel Number: : Channel 1]
[0F 00 E9 A0 83 00 01 00 01 ]
[NA Facility - NAS]
[0F 00 11 FD 11 00 A1 0F 02 01 01 02 01 A1 30 07 80 05 30 03 81 01 01 81 ]
[Trunk 2 09:20:56 > CC < CRef Origin: CRef 218E SETUP NAS 9792302913 87134364174]
[Bearer capability - Speech - G.711 u-law]
[Information Transfer Capability: speech]
[Coding Standard: CCITT standardized coding]
[Information Transfer Rate: 64 Kbits/s]
[Transfer Mode: circuit mode]
[User Information L1 Protocol ID: Recommendation G.711 u-law]
[Layer and Protocol Identification: User Information L1 Protocol]
[13 00 81 90 00 00 A2 00 00 00 00 00 00 00 ]
[Channel identification - 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: 0]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : ]
[0F 00 69 00 83 00 01 00 81 00 ]
[NA Facility - NAS]
[0F 00 11 FD 11 00 A1 0F 02 01 01 02 01 A1 30 07 80 05 30 03 81 01 01 09 ]
[Calling party number - E.164/National - 9792302913]
[Numbering Plan Identification: ISDN/Telephony numbering plan (Rec. E.164)]
[Type of Number: National Number]
[Screening indicator: User provided, not screened]
[Presentation indicator: Presentation allowed]
[Number Digits: - 9792302913]
[07 00 21 80 0A 00 09 07 09 02 03 0A 02 09 01 03 ]
[Called party number - Unknown/Unknown - 87134364174]
[Numbering Plan Identification: Unknown]
[Type of Number: Unknown/Reserved Value]
[Number Digits: - 87134364174]
[03 00 80 00 0B 00 08 07 01 03 04 03 06 04 01 07 04 ]
[Trunk 2 09:21:00 < CC > CRef Origin: CRef 226 DISCONNECT Reject]
[Cause - Reject]
[Location: User]
[Coding Standard: CCITT standardized coding as described below]
[Cause Class: Normal Event]
[Cause: Call rejected]
[05 00 80 00 15 00 ]
[Trunk 1 09:21:04 > CC < CRef Origin: CRef 22C7 DISCONNECT Normal]
[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 ]
[Trunk 1 09:21:04 < CC > CRef Origin: CRef 4 DISCONNECT Normal]
[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 ]
--------------------------------------------------------

[Line Monitor]

[Statistics]
[Active Lines] "0"
[Line Monitor]
[Line: 1 - Line001 Direction: Incoming Start Time: Mon Jun 18 09:20:56 2007 State: Idle Number and Name: 9792302913 - ? DNIS: 871343644 ]
[Line: 2 - Line002 Start Time: Mon Jun 18 09:21:10 2007 State: Idle ]
[Line: 4 - Line004 Direction: Outgoing Start Time: Fri Jun 15 09:27:52 2007 User: 5002 - Judy 1 State: Idle Number and Name: 2908 ]
[Line: 5 - Line005 Direction: Outgoing Start Time: Mon Jun 18 09:16:47 2007 User: L65 - ? State: Idle Duration: 00:00:21 Number and Name: 2919 ]
[Line: 6 - Line006 Direction: Outgoing Start Time: Mon Jun 18 09:15:13 2007 User: 5012 - Ron State: Idle Duration: 00:03:29 Number and Name: 3333 ]
[Line: 65 - Line065 Direction: Incoming Start Time: Mon Jun 18 09:16:47 2007 User: L5 - ? State: Idle Duration: 00:00:21 Number and Name: 8326300651 - ? DNIS: 7100 ]
[Line: 66 - Line066 Direction: Incoming Start Time: Sat Jun 16 09:44:53 2007 User: L5 - ? State: Idle Number and Name: 9792993174 - ? DNIS: 7101 ]
[Line: 69 - Line069 Direction: Outgoing Start Time: Fri Jun 15 14:40:56 2007 User: ? - ? State: Idle Number and Name: 2814671480 ]
[Line: 70 - Line070 Direction: Outgoing Start Time: Fri Jun 15 14:39:40 2007 User: 5005 - Christy State: Idle Number and Name: 18664417031 ]
[Line: 71 - Line071 Direction: Outgoing Start Time: Mon Jun 18 09:21:06 2007 User: ? - ? State: Idle Number and Name: 7134364174 ]
[Line: 72 - Line072 Direction: Outgoing Start Time: Mon Jun 18 09:22:33 2007 User: 5012 - Ron State: Idle Duration: 00:00:29 Number and Name: 7138230425 ]
--------------------------------------------------------

[Usage Indicators]

[BCM Info]
[CPU] "0%"
[Physical memory (MB)] "83 of 251"
[Physical memory (MB)] "33%"
[Nonpaged mem. (MB)] "0 of 97"
[Nonpaged mem. (MB)] "0%"

[Used Media Card Resources]
[Signaling channels] "22 of 72"
[Signaling channels] "31%"
[Media channels] "83 of 160"
[Media channels] "52%"
[Voice bus channels] "N/A"
[Voice bus channels] "N/A"
[DSP resources] "12 of 60"
[DSP resources] "20%"

[Active Telephony Devices]
[IP trunks] "0 of 6"
[IP trunks] "0%"
[IP sets] "0 of 1"
[IP sets] "0%"
[Voice ports] "1 of 11"
[Voice ports] "9%"
[Media gateways] "0 of 2"
[Media gateways] "0%"
--------------------------------------------------------
 
What is your access code for the local PSTN? 9? If so, why set up the 8? Why not just use the 9 for both types of calls and allow the system to route the call over VoIP or PSTN as necessary? It would be so much easier to setup and troubleshoot.

The only reason that I could see given the info you've provided is that you're either not sending the correct digits/call type or you have all trunks busy when testing.

Can you post your routes/Dest Codes for both ends?
 
Neither the VoIP lines nor the PRI on the other end are full.. that was my first thought but I ruled that out using BCM monitor. The other strange thing is that it only happens with the 8713 number, not the 8281 numbers. And yes, we dial a 9 to get out here. It was originally set up using a 9281 to route to the other end, but for reasons unbeknownst to me, it was changed. I hate to set it up using the 9281 routes and still have trouble with it. Here are my routes/destination codes:(I am in Clute switching out in Manvel - the other branches are connected via a T1 but no PRI coming in to them). Let me know if anything else would be helpful. Thanks again for the help!
Originating end:


4 002 0 false false false false false false false false false false

50 002 0 false false false false false false false false false false

60A 002 0 true true true true true true true true true true

6979 003 0 false false false false false false false false false false

70 003 All false false false false false false false false false false

8281 003 0 false false false false false false false false false false

8713 003 0 false false false false false false false false false false

8832 003 0 false false false false false false false false false false

8979 001 1 false false false false false false false false false false

9 001 All false false false false false false false false false false


Routing tables:
alvin 6000 6001 6002 6003 6004 6005 6006 172.16.6.55 BCM CSE H323 false 0.0

lakejackson 4 6979 172.16.2.55 BCM CSE H323 false 0.0

manvel 5 9 8713 8281 8832 172.16.4.55 BCM CSE H323 false 0.0




The end that switches out the call:
29A 001 0 true true true true true true true true true true

30A 001 0 true true true true true true true true true true

3333 001 0 false false false false false false false false false false

40A 001 0 true true true true true true true true true true

599 003 2 false false false false false false false false false false

60A 001 0 true true true true true true true true true true

8281 002 1 false false false false false false false false false false

8713 002 1 false false false false false false false false false false

8832 002 1 false false false false false false false false false false

9979 003 0 false false false false false false false false false false

9A 002 1 true true true true true true true true true false



alvin 6 172.16.6.55 BCM36 None false 0.0

clute 3 29 9 3333 172.16.1.55 BCM36 CSE false 0.0

lake_jackson 4 172.16.2.55 BCM36 None false 0.0

 
Try changing the call type on the 8713 to a National call type on the Clute BCM. Aborb the 8 and insert the PSTN access code at Manvel in the External number field.

Also enusre that all your VoIp trunks are using the correct remote access package at both sides.
 
Ok, let me make sure I understand your instructions.
1) In Clute, under Dialing plan -> Routing -> routes, I changed the DN type from Public(unknown) to national. No effect.
2) In Manvel, absorb the 8 under the destination codes tab. (Already being done). Under the Routes tab, put a 9 in the external number field for that route. I tried that and then a get a recording saying "please dial a 1" because it is actually dialing the 9 in the number.
3) I had to research what a Remote access package was (I still don't really understand what they are) but I found the cause of my problem. Under Call security -> Remote access packages, package 1 and 2 were checked for both systems. Also package 1 was assigned to each line under Active VoIP lines on both sides. However, in all but line 1 on the Manvel side, there were numbers in the line and remote restrictions. I changed these to 0, and now all the lines can be active at once.

Problem solved, thank you very much! I would have never found it.
 
There is a MUCH cleaner way to do what you have done, but as long as you found the root cause of your problem, Excellent.
 
Remote Package is what is used by the Host system to allow Remote users (in your case the other system) to use it's lines to make calls. If your Remote Package does not match on the Inbound Lines and Outbound Lines of the Host then the call will not complete.
 
Thanks for the info hawks. Since we have 4 locations, should the remote package all match on all 4 systems, ie have a 1 in there? It was really messy when I inherited it, one branch would have a 1 for remote package and another have a 2. I don't know why.

Also, I would certainly appreciate any pointers on making this "cleaner".
 
It all depends on how the Remote Package is set up with dialing Filters. For Admin purposes I try to make mine the same but if this is something that you inherited that might mean a lot reprogramming for you. Like stated earlier the main thing is the inbound lines and the outbound lines of the host system need to have the same remote pkg assigned to them.. good luck
 
The Much cleaner way would be to do away with dialing a diffferent access code to use another systems trunks and make it transparent to the end user.

If you already have 4 sites that you are linking, it would be worth adding an NRS to the system. Once that is in place and properly set up, users just dial 9-1-NPA-NXX-XXXX (for calls that are LD to their site) and let the systems decide how to route the call over the VoIP. You can even set it up so that the call will fail back to the PSTN should there be no VoIP facilities available.

This centralizes the database and makes it SUPREMELY easy to add sites later. Simply create a new endpoint in NRS with the appropriate CDP and e.164 entries and when your new site comes on line all the other sites can access its facilities immediately.

With the right info in place, a four site setup shouldn't take more than 8 or so hours to get going, and most of that time is in the data entry in NRS. Further sites would only take about 2-3 hours tops to add.

I have a customer right now who originally contracted 5 sites (4 BCMs each with 2 NPAs in each local calling area and a an Option 11 with cabinets at 3 sites with 5 NPAs in the local calling area) across Canada. They now save over $9k/mth in LD. I just added a sixth BCM this past week (2 more NPAs) and it took me about 3 hours to enter the stuff in the BCM and NRS. All dialing is transparent to the end user.

It DOES take some planning and management, but it is a really SWEET setup.

Just my HO.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top