First, I apologize that I may have sent a similar question to this one before, but I was unable to locate it when I did a search on the site.
We have two PRIs that appear to be configured exactly the same on our side (as far as the route and the ADAN D-channel info are concerned). Not sure if I should be looking somewhere else. One of the PRIs sends name and number to the distant end and one sends only number. We would like both to send only the number. Although I think the carrier has the issue and they have indicated the PRIs were provisioned with different protocols (one with NI1, the other ???). However, I don't see where we provide this on the Nortel side --- assuming they need to match.
The carrier indicated I should check LD 16 to see if we could block. I suppose it is possible that we are sending both name and number on both and the CO is blocking on one and not the other. If this is possible then maybe the fix is within my control. Is anyone familiar with this issue?
In LD 16, I came across
NCNA (YES) NO Network Calling Name Allowed
In some documentation I located something indicating I could suppress calling name display with CPP as a FFC or not allowing NDS (Name Display Services), but not sure this applies as although my ADAN info has NDS for the RCAP prompt, it has D100 for the IFC (thinking maybe the name display stuff works if IFC is NI2).
Any suggestions would be appreciated.
We have two PRIs that appear to be configured exactly the same on our side (as far as the route and the ADAN D-channel info are concerned). Not sure if I should be looking somewhere else. One of the PRIs sends name and number to the distant end and one sends only number. We would like both to send only the number. Although I think the carrier has the issue and they have indicated the PRIs were provisioned with different protocols (one with NI1, the other ???). However, I don't see where we provide this on the Nortel side --- assuming they need to match.
The carrier indicated I should check LD 16 to see if we could block. I suppose it is possible that we are sending both name and number on both and the CO is blocking on one and not the other. If this is possible then maybe the fix is within my control. Is anyone familiar with this issue?
In LD 16, I came across
NCNA (YES) NO Network Calling Name Allowed
In some documentation I located something indicating I could suppress calling name display with CPP as a FFC or not allowing NDS (Name Display Services), but not sure this applies as although my ADAN info has NDS for the RCAP prompt, it has D100 for the IFC (thinking maybe the name display stuff works if IFC is NI2).
Any suggestions would be appreciated.