One-X VoIP Caller ID

[danisrael]

We have a One-X up and running on VoIP. The Calls seem to work fine with the exception that outbound calls have No Caller ID and therefore are send as PRIVATE, WITHHELD, or NO CALLER ID by the called party.

When I look at the difference between a standard call and One-X Mobility VoIP call in SysMonitor, I'm not able to see anything more than the 4 Digit Extension number for Calling Party in either case.

08:43:01 35652833mS CMTARGET: ISDN BChannel 20: in-service check = 1
08:43:01 35652835mS CMARS: FOUND LINE - Line Id: 1 - using line group id: 0 - Called Number: 808xxxyyyy - Calling Number: 6725

Any ideas on this or how to troubleshoot it through monitor?

 

[Telecomboy]

Are your inbound call routes built using only 4-digits? If so, change them to 10-digit.

 

[danisrael]

Telecomboy, The actual "Incoming Call Routes" > Incoming Number is a 10 digit number, but the Destinations are set with the drop down box which shows the user 4 digit extension and Name. Are you saying set the extension length to 10 digits?

 

[Telecomboy]

Nope. The incoming number should be 10-digits as you have it so that isn't the issue.

 

[amriddle01]

Use user shortcodes to send the required caller ID

 

[danisrael]

amriddle01, the Caller ID works properly from IP & Digital phones. It is only when a user is logged in through VoIP on the One-X mobility. Is there a way to put the codes in the iPhone app. I experimented with the dialing plans in the Mobility app...but it won't allow shortcodes.

 

[amriddle01]

I am guessing it isn't checking ICR for DDIs when using the App as it does with a desk phone, try the user shortcodes...it can't hurt

 

[danisrael]

amriddle01, It works using a shortcode. But when I do this, it kills the ability for the user to use system shortcodes. Is there a way to use both?

 

[danisrael]

Fixed that. We have eliminate Dial 9 so the myriad of apps can dial out. Had to match the ARS in the user's section. Kind of a pain. I wish this worked without the workaround.

 

[danisrael]

Well...this isn't really a valid work around as it breaks the ability for internal callers CLID to be sent and seen. Anyone else have any ideas?

 

[danisrael]

I've opened an IPOSS ticket as I now believe this to be a bug. There appears to be additional characters after the Calling Party number is sent.

STANDARD HANDSET
12:57:37 2685157306mS CMLineTx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=0 id=142184 in=0
Called[XXXXXX8055] Type=National (2) Reason=CMDRdirect Calling[highlight #FCE94F][XXXXXX6725][/highlight] Type=National Plan=ISDN
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=0 chan=23
Locale: enu


ONE-X MOBILE
13:09:15 2685856725mS CMLineTx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=0 id=142275 in=0
Called[XXXXXXX8055] Type=National (2) Reason=CMDRdirect Calling[highlight #FCE94F][XXXXXXX6725[/highlight]] Type=National Plan=ISDN
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=0 chan=23
Locale: enu

 

[danisrael]

This was indeed a bug and has been resolved in 9.0.6 (SP6 March 2015).