I'm trying to get QSIG working between CCM 4.1(3) and some Nortel
PBXs. In order to solve a couple of different problems, I had to
change some settings that cisco recommends leaving at the default.

On the gateway configuration page, I changed "Calling party IE number
type unknown" to Subscriber (default is CallManager) and I changed
"Calling Numbering Plan" to Private (default is CallManager).

We have a centralized Meridian Mail system and these settings solved
some problems for us. However, I'll be honest and say that I don't
know exactly what these settings do and I haven't been able to
determine the details from reading the documentation. Are there any
possible future consequences I should be aware of?

Thanks!
John

[ Post a follow-up to this message ]

Those settings are present for exactly what you did.  Various PBX
configurations require different values.  The settings you changed
affect the Numbering Plan and Numbering Type fields for the calling
party in the SETUP sent over the ISDN connection to the PBX.

/Wes

John Neiberger wrote:
> I'm trying to get QSIG working between CCM 4.1(3) and some Nortel
> PBXs. In order to solve a couple of different problems, I had to
> change some settings that cisco recommends leaving at the default.
>
> On the gateway configuration page, I changed "Calling party IE number
> type unknown" to Subscriber (default is CallManager) and I changed
> "Calling Numbering Plan" to Private (default is CallManager).
>
> We have a centralized Meridian Mail system and these settings solved
> some problems for us. However, I'll be honest and say that I don't
> know exactly what these settings do and I haven't been able to
> determine the details from reading the documentation. Are there any
> possible future consequences I should be aware of?
>
> Thanks!
> John
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

I discovered a problem with hard-setting these parameters this
morning. By manually making CallManager present calls as
Private/Subscriber, our Meridian Mail system thinks all calls are
internal even if they're external. If an external caller calls a DID
number at our test site and the call rolls to voice mail, they now
here the internal greeting instead of the external greeting.

Right now we are only passing internal four-digit calls over the QSIG
trunks, but there are going to be some situations where 10-digit
local, LD, and international calls may need to go over these trunks. I
have a suspicion that those might fail, or at least behave strangely,
if I leave these settings manually configured.

What I really need is a way to make CCM behave more like the Nortel
PBX, i.e. dynamically set the calling settings to Private/Subscriber
for internal calls but leave them at unknown/unknown for external
calls. It's setting them to unknown/unknown for both internal and
external calls.

Ideally, this would be configurable on the route pattern configuration
page but there is no such parameter there.

John

On 8/31/06, Wes Sisk <wsisk@cisco.com> wrote:
> Those settings are present for exactly what you did.  Various PBX
> configurations require different values.  The settings you changed
> affect the Numbering Plan and Numbering Type fields for the calling
> party in the SETUP sent over the ISDN connection to the PBX.
>
> /Wes
>
> John Neiberger wrote: 
>

[ Post a follow-up to this message ]