Vega 100G missing first letter of inbound CNAM

We’re using a Vega 100G as a gateway between our ISDN PRI provider’s interface and our FreePBX system. When we get an inbound call, the CID appears fine but the CNAM is missing the first letter for all of the calls we receive.

I spoke with our provider (Cox Communications) and their tier II says that their equipment is showing that it’s pushing the full CNAM out from their end. Is there an setting for the T1 interface that I’m missing? Any help would be appreciated.

This is what the Vega log shows for the inbound call:

LOG: 09/27/2019 10:31:24.390 ISDN (I)R01C02 incoming
call ref=[f100059e] srce=TEL:8442431545,DISP:OX COMMUNICATI [0]

LOG: 09/27/2019 10:31:24.390 ROUTER (I)R0bC00 FINDROUTE profile:1(Legacy) plan:1
call ref=[f100059e] <-- ISDN [1,1] dest=TEL:9774
–> SIP [2,1] dest=TEL:9774

LOG: 09/27/2019 10:31:24.390 ROUTER (I)R0bC00 call proceeding
call ref=[f100059e]

LOG: 09/27/2019 10:31:30.735 SIP (I)R03C17 connect g711Ulaw64k (Profile 1 - Voice)
call ref=[f100059e]

LOG: 09/27/2019 10:38:18.840 ISDN (I)R04C02 disconnect 16
call ref=[f100059e]

LOG: 09/27/2019 10:38:18.840 ISDN (I)R04C02 send release 16
call ref=[f100059e]

LOG: 09/27/2019 10:38:18.840 SIP (I)R04C10 disconnect(disc req) 16
call ref=[f100059e]

The inbound CNAM is from Cox Communications and they said that they’re sending 15 characters. As you can see the CNAM in the log is only 14 characters with the missing first letter.

that is odd - please open a ticket with us on the matter and we’ll get you an answer

Ok. I’ll put in a ticket as soon as the Vega is listed in my support portal (it’s another ticket in process).

Jason,

Did you ever find out the reason for the first letter getting dropped?

We are experiencing the same issue.

Thank you!

I had left the T1 Network Protocol set to auto and it turns out that the Vega selected DMS as the protocol. While largely compatible and it did work for phone calls, the CNAM info didn’t quite work with that protocol. I manually selected national (NI) and it started working.

2 Likes

Jason,
Your fix worked perfectly.
Thank you so much for your help.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.