Tracking down Caller ID

[skeating]

Hello

I am trying to find in CallAttendant where the Caller ID is listed. I am working with my phone service provider, and they are looking for where this is setup. When we normally call out, the number 703-406-3000 displays on the receiving end, but now it occasionally  shows up as 7 03 406 3000, and will display the Caller ID Russia. So I am trying to make sure nothing on our side is causing the problem. Is there a command in the Avaya Site Administrator that would show me this information?

Thanks

Stephen Keating

[jayh]

Not really enough information. Is your phone provider SIP and the PBX connected by PRI?

Look for settings in the PBX for e.164 and try that.

Map the ISDN number-template to national for the pattern generated by the PBX.

Try sending the caller-id with a leading 1 (country code)

Call your carrier and ask them to stop doing that.

[skeating]

I am working with my phone provider, and they were asking about the Caller ID. We are using IPCOMMS SIP and a Digium PBX. I know when we call out the 703-406-3000 appears on the receiving end, I was just trying to figure out if that was put into the CallAttendant service and if so where. I looked on the Digium, and there is no Caller ID and no setting for the number.

[jayh]

skeating wrote:

I am working with my phone provider, and they were asking about the Caller ID. We are using IPCOMMS SIP and a Digium PBX. I know when we call out the 703-406-3000 appears on the receiving end, I was just trying to figure out if that was put into the CallAttendant service and if so where. I looked on the Digium, and there is no Caller ID and no setting for the number.

"Is there a command in the Avaya Site Administrator that would show me this information?"

Where does Avaya fit into this?

What Adtran equipment is between the Digium PBX and the carrier?

[skeating]

Avaya is the phone system which we are using. It goes through an Avaya S8300 Media Server, then to the Digium G100 Gateway, then to the cloud, in our case IPCOMMS. The phone number, 703-406-3000, is provided by IPCOMMS (actually we have had it for several years, porting it to each phone company). I am trying to rule out that the Caller ID is somehow configured in our equipment.

[jayh]

skeating wrote:

Avaya is the phone system which we are using. It goes through an Avaya S8300 Media Server, then to the Digium G100 Gateway, then to the cloud, in our case IPCOMMS. The phone number, 703-406-3000, is provided by IPCOMMS (actually we have had it for several years, porting it to each phone company). I am trying to rule out that the Caller ID is somehow configured in our equipment.

What Adtran gear is in the mix? When you send the SIP invite to IPCOMMS, what is shown as "From" and "Contact"?

[skeating]

Sorry to show my ignorance, but how do you send an SIP invite to IPCOMMS? Is there somewhere in the CallAttendant/S8300 Server I can find, or run the command?

[jayh]

A SIP invite is the initial message sent when making a call. It happens every time a call is placed.

1. What Adtran equipment is involved in this setup?
2. What is the handoff between the Avaya and the Digium? Is it PRI, Ethernet, etc.?
3. What is the handoff between the Digium and IPCOMMS? Is it PRI, Ethernet, etc.?

[skeating]

The S8300 was part of the Adtran install of the Avaya phone system. The handoff between the Avaya ant the Digium is Ethernet. The hadoff between the Digium and IPCOMMS is PRI.

[jayh]

skeating wrote:

The handoff between the Digium and IPCOMMS is PRI.

Consult your Digium documentation, or contact Digium support to find out how to configure the calling party number isdn numbering plan and isdn type-of-number both as national on the PRI facing IPCOMMS. It is probably presently unknown or not specified. 

The caller-id on a call originating to the PSTN via PRI is set by the PRI as part of the SETUP message. (but can be overridden by the carrier). It's specified as calling party number. There's also a field in the SETUP message that tells the other end what type of number it is. If you set it as national, then the carrier should treat it as a NANPA number with the appropriate country code. Otherwise, some terminating carriers may parse the first few digits as a country code.

This should fix it, but if it doesn't work, try setting the outbound caller-ID in the Digium as 1-703-406-3000.

[Anonymous]

I deal with this all the time on a carrier perspective. Caller ID is becoming more of a mess but here is how to fix it.

In the Q.931 SETUP message there is a 'Calling Party Number' section. Here is an example:

Calling Party Number                   Length =  12
     Type of Number                 National Number
     Numbering Plan      ISDN/Telephony E.164/E.163
     Presentation Indicator                 Allowed
     Screening Indicator    User Provide, no Screen
     Number                              NPANXXXXXX

The four sections must be configured as:

(1) Nature of Address Indicator: National number
(2) Numbering Plan: ISDN (telephony) numbering plan/E.164
(3) Presentation Indicator: Presentation Allowed
(4) Screening indicator: two of four are good, Provided/Screened/Passed is the best option of the four.
     00     user provided, not verified            Not supported
     01     user provided, verified and passed     Supported
     10     user provided, verified and failed     Not supported
     11     network provided                       Supported

The example above the screening was incorrect. Once corrected, caller ID passed to both wireless and wireline with no issues. Most gateways are mapped to what they receive so you might have to check upstream on what is received.

[skeating · Accepted solution]

The solution came from our phone provider. They made some change on their side, and the problem was solved. They did have me add a '1' to the number for us.

Thanks for your assistance on this problem.