I am networking 3 BCM 50's and trying to use 4 digit dialing between the 3. Site 1 is using 2200 series, site 2 is using 2300, site 3 is using 2400. I have everything programmed to what I believe is correct. Destination digits of 22, 23, 24; routing set up, ip addresses configured. However, I am getting fast busy when I dial out using 4 digit dialing. I've opened the monitor, and all digits are being sent. Any ideas?
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!
Networking 3 BCM 50's 1
- Thread starter rval80
- Start date
- Thread starter
- #3
- Thread starter
- #4
- Thread starter
- #5
- Thread starter
- #7
Few tips:
1) take care that an incoming call is not being routed out on the BCM you are calling.
2) If you have digital sets on the BCMs, try dialling from digital set on one BCM to a digital set on the intended BCM....thay way you are testing the signalling and media path BCM to BCM, and not to/from the IP sets.
3) Look at the feps log (this will give details from the perspective of the voip trunk, where it is SIP or H323)...
on both the BCM you are calling from and to,
a. Take a snap shot of the feps log before the call.
where xx.xx.xx.xx.xx is the IP address of your BCM/SRG.
Enter the nnadmin account and corresponding password as required.
b. Attempt the failed call.
c. Repeat step 1.
Does the feps log on the calling and called BCMs give an indication? Browsing the log file will not be available for BCM 4.0 or possibly earlier versions of 50, so you might need to make some test calls and collect the full set of logs, then extract them and look for feps.log.
regards
Paul
1) take care that an incoming call is not being routed out on the BCM you are calling.
2) If you have digital sets on the BCMs, try dialling from digital set on one BCM to a digital set on the intended BCM....thay way you are testing the signalling and media path BCM to BCM, and not to/from the IP sets.
3) Look at the feps log (this will give details from the perspective of the voip trunk, where it is SIP or H323)...
on both the BCM you are calling from and to,
a. Take a snap shot of the feps log before the call.
where xx.xx.xx.xx.xx is the IP address of your BCM/SRG.
Enter the nnadmin account and corresponding password as required.
b. Attempt the failed call.
c. Repeat step 1.
Does the feps log on the calling and called BCMs give an indication? Browsing the log file will not be available for BCM 4.0 or possibly earlier versions of 50, so you might need to make some test calls and collect the full set of logs, then extract them and look for feps.log.
regards
Paul
- Thread starter
- #11
-
1
- #12
If you have SIP trunks between your sites, make sure that your codecs are all set the same and that the payload sizes match.
If you're using IP sets to call to/from, make sure the payload sizes match that of you're trunks. I had that problem once and it took me 2 days to figure out what was causing that exact problem. Call would go through but disconnect as soon as the other end answered.
If you're using IP sets to call to/from, make sure the payload sizes match that of you're trunks. I had that problem once and it took me 2 days to figure out what was causing that exact problem. Call would go through but disconnect as soon as the other end answered.
- Thread starter
- #13
- Status
Similar threads
- Locked
- Question
