Issue with Mobility and Caller ID

Unanswered Question
Oct 16th, 2008

I am having an issue with Caller ID showing properly on the Cell Phone I have associated in Mobility. If I call from an internal extension to a mobility extension I have the transformation patterns set up for the proper Caller ID and everything works great. However if an outside caller calls the Mobility DID it shows up on the Cell phone with the main number of the company instead of the Persons who called Caller ID. I have run debug ISDN q931 and I see the correct caller ID (the person who called) being sent to the provider, but that is not what is showing up on the cell phone. The Gateway is running h323, other offices are running MGCP and they seem to work fine. (we can't switch to mgcp on this gateway). However when the call comes in on the PRI I do get this error

Ux_BadMsg: Invalid Message for call state 7

I think that has something to do with Caller Name that we are not setup for on our h323 gateway, so I am not sure if it is related to the issue. Any help would be appreciated.

Thanks

Ken

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Chris Deren Thu, 10/16/2008 - 15:49

It's most likely the carrier setting the caller ID to the BTN, you will need to work with them to allow you to pass the caller ID.

Chris

Sascha Monteiro Thu, 10/16/2008 - 19:09

can you show the q931 debug?

is the redirecting party field there too?

I believe the redirecting party needs to match your client's ID, otherwise the calling party id can be discarded. (imagine you could send ANY ID as calling aprty ;-o )

kgroves42 Fri, 10/17/2008 - 04:48

I think you are correct, the carrier is not allowing me to change the Caller ID to a number that is not in my block of DID's. What is the feature called to allow that? Because this works at other branches just not at one branch that uses verizon as the carrier.

Thanks

Ken

Actions

This Discussion