Alcatel Unleashed

To the best of my knowledge, the OXO up to software version 7.1 does not support SIP indial as it can't address the TO: field in a SIP header.

Can anybody confirm this and if so advise if the issue is solved in Ver 8.0?

Direct indial works fine on 7.1. Have you setup and tested? check numbering formats in the sip gatway as this needs to be correct in relation to the public numbering plan. Sip carriers normally send full number so you may need to strip the contry code.

Thanks Murray

I will certainly give it a go. The SIP carrier I am using here sends the indial details in the TO: Field so I am hoping the OXO is looking there as well when it does the indial number processing.

Do you mind me sending you the config file, for you to view, if those changes don't work for me?

Hello.

Have you solved this issue? I have the same problem.

Regards.

Not Really. Can't get an effective answer from any body. Best solution to to find a VOIP carrier that sends indial info in INVITE fiels as well as TO: field.

Hello Marc.

Thanks for your reply.

I have a problem. I am also parter of this provider, so I am forced to sell its service. I had to insert a Gateway to emulate ISDN ports and install a PBX with an ISDN configuration. I am trying to convince them to change the way they inform a call.

Apart form this limitation, I have another: when the OXO makes a call, the "from header" includes the caller number (f.e 986777777) and the "proxy authorization" the username, witch is different (f.e. 100-000999-01-001). The providers regets the call ("From username does not match digest credentials"). I can force the external Gateway to send the username (f.e. 100-000999-01-001) in the "from header" field, but I do not know how to do that in the OXO. Do you think it would be possible? I am pessimistic.

Regards.


Alejandro

Try
Subscriber -> Miscallaneous->Alternative CILP/COLP. Put the outgoing number required in here.

Thanks for your reply.

It would work it the username had an e164 format. I cannot write 100-000999-01-001 as an arternative CLIP/CLOP.

Regards.

Try putting your alternative CLIP/COLP number in Numbering - ARS - SIP Public Numbering. That helped me with one particular provider (on R8.0).

Hello.

Thanks for your interest.

I have tried your suggestion, but I cannot get the "From" to be the alterntative CLIP/CLOP. The "From" number is composed by the "instalation number" + "extesion number". In my case sip:98610@192.168.1.246, where 986 is the instalation number and 10 the extesion number. I have 8.0 and I do not what is wrong. Alternative number works when I configure it in T0, extensions, and instalation numbers, but not here.

Regards.


Alejandro