Trunk setup for correct ANI

[Ventus Logistics]

Hello. We have 7 offices with PBXNSIP on all of them and we have them interconnected. We have most of our PSTN traffic setup to go out our Audio Codes Mediant 1000 which has 2 trunks. One with a mexican carrier and another with a US carrier. Each carriers deleivers 100 DID's in both countries and they match to 1500 - 1599. We have our Remote Party/Privacy Indication: on the trunk set to P Prefered Identity in order to have our ANI's displayed correctly as we do alot of call forwarding of some of the DID's to different mobiles and land lines and we need the remote party number displayed. It has all been working great for sometime know.

 

Just last week we came into the need of having our user dialing into calling card DID or auto attendent DID and having them dial out via the PBX for cost and control reasons. We noticed that the called party was being displayed the orginal ANI which was coming from a mobile or remote land line. In order for us to get PBXNSIP to respect the ANI of the extension being used we have change the Remote Party/Privacy Indication:on the trunk to P Asserted Identity. With this the 2nd scenario works great but we loose the first scenario.

 

Is there any way to have more control over Remote Party/Privacy Indication: on a trunk? Maybe something where we can control via the extension/DID?

[Vodia PBX]

Hello. We have 7 offices with PBXNSIP on all of them and we have them interconnected. We have most of our PSTN traffic setup to go out our Audio Codes Mediant 1000 which has 2 trunks. One with a mexican carrier and another with a US carrier. Each carriers deleivers 100 DID's in both countries and they match to 1500 - 1599. We have our Remote Party/Privacy Indication: on the trunk set to P Prefered Identity in order to have our ANI's displayed correctly as we do alot of call forwarding of some of the DID's to different mobiles and land lines and we need the remote party number displayed. It has all been working great for sometime know.

 

Just last week we came into the need of having our user dialing into calling card DID or auto attendent DID and having them dial out via the PBX for cost and control reasons. We noticed that the called party was being displayed the orginal ANI which was coming from a mobile or remote land line. In order for us to get PBXNSIP to respect the ANI of the extension being used we have change the Remote Party/Privacy Indication:on the trunk to P Asserted Identity. With this the 2nd scenario works great but we loose the first scenario.

 

Is there any way to have more control over Remote Party/Privacy Indication: on a trunk? Maybe something where we can control via the extension/DID?

 

Remote-Party-ID is a old, obsolete Cisco proposal for indicating the remote party. It expired a couple of years ago. Everyone in this industry should better stop using it. We are too nice and we still offer it. I believe even Cisco does not offer it any more in the latest versions.

 

P-Asserted-Identity and P-Preferred-Identity made it to the RFC state. This is the way to go. AudioCodes as one of the better products in this industry fully supports it.

 

Regarding the cell phone redirection, there is the old problem: How can the gateway "trust" the PBX that this is not a spoofed caller-ID? Especially for ITSP that is a huge problem. Because of this, we introduced a new header called "Related-Call-ID" that indicates the original caller-ID. Not RFC yet, but at least CallCentric said they are going to support it and then the original caller-ID will show up on the cell phone. Bravo!

[Ventus Logistics]

Remote-Party-ID is a old, obsolete Cisco proposal for indicating the remote party. It expired a couple of years ago. Everyone in this industry should better stop using it. We are too nice and we still offer it. I believe even Cisco does not offer it any more in the latest versions.

 

P-Asserted-Identity and P-Preferred-Identity made it to the RFC state. This is the way to go. AudioCodes as one of the better products in this industry fully supports it.

 

Regarding the cell phone redirection, there is the old problem: How can the gateway "trust" the PBX that this is not a spoofed caller-ID? Especially for ITSP that is a huge problem. Because of this, we introduced a new header called "Related-Call-ID" that indicates the original caller-ID. Not RFC yet, but at least CallCentric said they are going to support it and then the original caller-ID will show up on the cell phone. Bravo!

 

Good morning. Please read my post more carefully. Remote Party ID/xxxx as I posted is also the name of the field in the trunk setup where you configure these options. I never mentioned I was using remote party ID. I am using Preferred and it works fine but it will not respect the ANI of an Extension even if you specify it under ext. config. In order to get this scenario to work of respecting your ANI config you have to use P-Asserted and then it works fine. The problem with P-Asserted is that we loose what we have working under P-Preffered which is having the original caller ID displayed on call forwarded calls.

 

So to sum up both scenarios work correct on PBXNSIP but my need is not to have one of them working at 1 time. I need both working simulteanously so our current setup will work 100%. How can this be acheived?

[Vodia PBX]

Good morning. Please read my post more carefully. Remote Party ID/xxxx as I posted is also the name of the field in the trunk setup where you configure these options. I never mentioned I was using remote party ID. I am using Preferred and it works fine but it will not respect the ANI of an Extension even if you specify it under ext. config. In order to get this scenario to work of respecting your ANI config you have to use P-Asserted and then it works fine. The problem with P-Asserted is that we loose what we have working under P-Preffered which is having the original caller ID displayed on call forwarded calls.

 

So to sum up both scenarios work correct on PBXNSIP but my need is not to have one of them working at 1 time. I need both working simulteanously so our current setup will work 100%. How can this be acheived?

 

It is still not clear to me what the setup is. Maybe you can include a little drawing. No big art, just something scribbled on paper and scan it...

 

Maybe the problem is that this is not a trunk call? ANI has no effect on calls that are to extensions.

[Ventus Logistics]

It is still not clear to me what the setup is. Maybe you can include a little drawing. No big art, just something scribbled on paper and scan it...

 

Maybe the problem is that this is not a trunk call? ANI has no effect on calls that are to extensions.

 

Sorry I am not big with forums or posting comments via text as it is more complicated to interpret. Is there any phone support even if it is paid so I can convey my message.

 

My scenario is dialing out to the PSTN where in some cases we need the calling party ANI to go through pbxnsip al the way to the destination #. This happenes when a PSTN (489-1500) user dials our DID 790-1509 which on the pbx is setup as extension 1509 with immediate call forward to 7631599. We want the original calling party (489-1500) ANI showed up on mobile 7631599 and this does happen with P-Preffered Identity setup on our trunk.

 

everything has been working great.

 

know we have a new scenario where we have 763-1599 calling the auto attendant and being authenticated by caller id and pressing 1 to place out bound calls to PSTN. we want to hide the 763-1599 ANI from end user receiving call on PSTN. but for that to work we have to setup trunk to P-Asserted Identity so it respects the ANI of the office extension (956-790-1509). so when we do this change we loos the previous working scenario.

 

so that is where my question comes into play to have both scenarios working what setup can we have? could you make the option on the extension setup to have P-Asserted Identity and override the trunk setup when you see this option.

[shopcomputer]

Sorry I am not big with forums or posting comments via text as it is more complicated to interpret. Is there any phone support even if it is paid so I can convey my message.

 

My scenario is dialing out to the PSTN where in some cases we need the calling party ANI to go through pbxnsip al the way to the destination #. This happenes when a PSTN (489-1500) user dials our DID 790-1509 which on the pbx is setup as extension 1509 with immediate call forward to 7631599. We want the original calling party (489-1500) ANI showed up on mobile 7631599 and this does happen with P-Preffered Identity setup on our trunk.

 

everything has been working great.

 

know we have a new scenario where we have 763-1599 calling the auto attendant and being authenticated by caller id and pressing 1 to place out bound calls to PSTN. we want to hide the 763-1599 ANI from end user receiving call on PSTN. but for that to work we have to setup trunk to P-Asserted Identity so it respects the ANI of the office extension (956-790-1509). so when we do this change we loos the previous working scenario.

 

so that is where my question comes into play to have both scenarios working what setup can we have? could you make the option on the extension setup to have P-Asserted Identity and override the trunk setup when you see this option.

 

If I understand this, he is trying to block the cell phones number from displaying as the outbound caller ID, this was supposedly fixed in version 3.2, thus far most ITSP's I tried still display the cell phone.

[Vodia PBX]

If I understand this, he is trying to block the cell phones number from displaying as the outbound caller ID, this was supposedly fixed in version 3.2, thus far most ITSP's I tried still display the cell phone.

 

Oh you mean for the DISA feature when calling from the call phone?

[shopcomputer]

Oh you mean for the DISA feature when calling from the call phone?

I think he is talking about, http://wiki.pbxnsip.com/index.php/Release_..._3.1#Cell_Phone

 

Also, when the cell phone was used to place an outbound call, the PBX sometimes presented the Caller-ID of the cell phone, not the extension. The purpose was to hide it. That was fixed, and now users can use their cell phones to place outbound calls and present the caller-ID of the PBX.

 

For most cases this problem still exists, I did manage to get it working with 1 ITSP, creating an inbound trunk and an outbound trunk, and some how forcing it to display the trunk ANI.

[Ventus Logistics]

I think he is talking about, http://wiki.pbxnsip.com/index.php/Release_..._3.1#Cell_Phone

 

Also, when the cell phone was used to place an outbound call, the PBX sometimes presented the Caller-ID of the cell phone, not the extension. The purpose was to hide it. That was fixed, and now users can use their cell phones to place outbound calls and present the caller-ID of the PBX.

 

For most cases this problem still exists, I did manage to get it working with 1 ITSP, creating an inbound trunk and an outbound trunk, and some how forcing it to display the trunk ANI.

Hello All. Sorry if i dont explain my situation clearly. let me go back to basics.

 

I have both scenarios working perfectly with pbxnsip and my PRI provider that connect to my audiocodes mediant 1000. The problem is that I cannot mix both scenarios. If I make scenario 1 work I have the issue scenario 2 stops working and vice versa.

 

My need is to having both scenarios at the same time work.

 

1.) When the owner of the extension dials in to the DISA or AA (pbxnsip) from the mobile (763-1599) and dials out to the PSTN I need for the receiving party to see the pbxnsip ANI (790-1509) setup on his extension. For this to work I have to setup the remote party ID on the trunk to be P Asserted Identity.

 

2.) When any person in the world dials from the PSTN (example 722-5026) into our pbxnsip user DID 790-1509 the call is immediatly forwarded to that user mobile # 763-1599 and we need our mobile user to be able to identify who the caller is via there caller id (722-5026). For this to work I have to setup the remote party ID on the trunk to P Prefered Identiy.

 

As you see above both scenario 1 and 2 work great on individual cases. The problem starts when I want to have both scenarios working at the same time as we only have 1 setting available for the trunk.

 

The solution I see is having an option to set 2 type of identities on a trunk and be able to have it use a specific type when the call is being generated via DISA or AA. If the call is just a redirect or immediate call forward or rest of the scenarios use the other type of identity.

 

You might ask why our world is so complicated and the reason is for tricking our mobile carriers that the call is always coming from a particular number for the office users that dont have unlimited mobile plans and this saves us a lot of money on our mobile bills using there friends and family plans. For the rest of our users that do have unlimited plans or regular plans we do need them to see the original caller ID coming in.

 

thanks for your help and I hope i was able to explain better this time.