Quote:
| Originally Posted by dzembek We were told by our carrier that it may have something to do with the type of call signalling being sent. Supposedly we're seeing the problem with 3.1KHZ calls vs. 64KHz calls? I saw a few references to this type of problem on the web with regards to ISDN, but nothing concrete. - One mentioned ensuring DSEL was set to 3VCE - One mentioned that some PBX's can be configured not to accept these types of calls and another said that the carrier can configure not to accept these types of calls. My local Nortel folks have been working hard to resolve, and I know I haven't provided a lot of info here, but I was curious if anyone else had run into anything like this before? Thanks! |
Basically if you're tandeming a call through a PBX you need to ensure that the trunk group that is being tandemed to has the same (or better) bearer capability as the group it's coming from, in this case if your TIE between PBXs is only a VCE (voice only) and the incoming PRI is setup up to handle 3VCE (voice and data) then any calls that come in as a 3.1 data will not tandem to the VCE route.
The vast majority of voice calls will come with that flag in the PRI message however I have seen a rare few calls come in from residential telephones that were voice calls but carried the 3.1 data flag, not sure why and never really followed up on it.