SIP Trunk, sending network provided no. instead of user provided no

[derfloh]

Hey guys,

after getting some excelent help from here I now have another question.

One of our customers her in germany is using a SIP trunk for external calls. Lets say his numbers are 09876/1234-xx where xx are extension numbers from 00-99. Because of growing of the company the customer decided to use three digit extensions. I talked to the provider and was told that this would not be a problem sind Clip-No-Screening is activated on the trunk so that I can send any outgoing number I want to...

But... and here is my problem... With every outgoing call only two of three extension digits are send to my mobile phone. I watched the monitor traces and I could see that all digits are sent.

I talked to the provider an he told me that I send a 'network provided number' which will be cut after the second extension digit by the providers switch. He told me that I have to send a 'user provided number' which will nt be cut or changed by the provider. My problem is that I have no idea how I can tell my IPO (6.0.14) how to send the number as a 'user provided number'.

I hope to get some useful hints because the customer is not very hapy about the fact, that his customers see one digit too less on their phones...

Thanks in advance...

 

[Westi]

How do you send the digits right now?
If you can see the entire length of the digits go out in the monitor trace then your line provider is full of hot air and just doesn't know how to change their settings.
If you send the caller ID right now then you probably send 09876-1234E out, so you send the number plus the extension number and that means if you change your extensions then it should send the new extension length out after the basic number.
for testing purposed change the outgoing number to 09876-123E and see if that then shows up on your mobile properly

Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[derfloh]

Hi Westi,

the digits are sent like they are in the user's SIP-Tab (098761234531).

098761234E doesn't work with SIP-Trunks. You have to type the outgoing number in the users SIP-Tab.

But thank you for your answer though.

 

[derfloh]

Hi there,

i got another Information from the Provider.

He told me that I have to send the CPN as an "additional calling party number". I should add that Information in the "P-Prefferred-Identity-Header".

Are ther any ideas how to do that?

Thanks in advance...

 

[Duffman88]

The URI you are using for outbound is set as "Use User Data" and all the users all have their SIP tab info populated with full numbers?

Chris
ACA- Implement IP Office

 

[derfloh]

Yes Chris,

if I use "Use Auth Data" I will just send 0987612340. I use "User Data" and I can see in the Monitor Trace that IPO sends the whole number like I wrote it into the user's SIP tab. But the provider told that the last digit will be automatically erased by his switch because I send a "Network Provided Number" instead of "User Provided Number".

 

[Duffman88]

That's what I thought I just like to double check the obvious sometimes

That's strange I've never heard that before.

Chris
ACA- Implement IP Office

 

[derfloh]

I think no one has... :-(

The customer is getting angry but no one knows how to change that.

Everything could be so easy with ISDN...

 

[Duffman88]

From what I am reading the IP Office only uses PPI for Privacy/Anonymous calls. Otherwise it is simply using the URI in the from field to set its identity and caller id. Most carriers/providers support simply using the From field and URI, but you found yourself a picky one. If you can get on with an Avaya engineer they may have a Source Number you can enter which will modify the SIP behavior to send your caller id via the PPI. Otherwise may be time to research new providers if it is a feature your customer must have.

http://support.avaya.com/css/P8/documents/100113683

http://www.rfc-editor.org/rfc/rfc3325.txt

I don't know Avaya doesn't have ALL of the source number variables readily available for the field tech's & engineers, but that's just the way it is. Only a few are published and the others you have to scratch and claw to find. Unless anyone has any secret docs they want to fill me in with

Chris
ACA- Implement IP Office