Incoming calls from mobile phones through a public SIP Trunk to an OXO Connect R2.1 are rejected

[aurelian]

Hello!

I have problems with incoming calls from mobile phones to an OXO Connect R2.1_037_001 connected through a public SIP Trunk. Incoming calls from fixed networks are OK. Outgoing calls are OK both in fixed networks and in mobile networks.

OXO rejects calls from mobile phones because INVITE messages from provider contain the header:

P-Access-Network-Info: GEN-ACCESS;"area-number=+4xxxxxxxxxxxxxx"

And OXO answer is:

Session Initiation Protocol (400)
Status-Line: SIP/2.0 400 Bad Request
Message Header
Warning: 399 192.168.100.239 "Malformed headers : P-Access-Network-Info "

The question is how could OXO not reject the communication?

[giovanni.attolini]

This header part was implemented on RFC3455.

Have you verified if OXO is RFC3455 compliant?

[aurelian]

Honestly, the client does not need RFC3455 implementation, OXO just needs to ignore this location information. But the provider does not want or can not remove this information from INVITEs. Does anyone know the meaning of the VOIPnwaddr flag bytes?

[enio.eltz]

Hi aurelian

As giovanni.attolini wrote, it is necessary to check if OXO is compliant with RFC3455. Looking for OXO datasheet, it does not mention that RFC:

Trunk standards compliance
RFC 3261, RFC 3261, RFC 3262, RFC 3264, RFC 2327, RFC 2833, RFC 2822, RFC 3515, RFC 360, RFC 3966, RFC 3398, RFC 3323, RFC 3324, RFC 3325, RFC 3892, RFC 1321, RFC 2617, T38 ITU-T, RFC 3263, RFC 4244, RFC 4904, RFC 3605, RFC 3326, RFC 3840, RFC 4028, RFC 3581, RFC 4916, RFC 3052, RFC 3327, RFC 4566, RFC 6140, TS 24.229

So, OXO can not deal that information, as I understand.

Is your SIP provider a certified one by Alcatel-Lucent? What is it?

VOIPnwaddr does not mention that RFC.

Best regards.

[aurelian]

Hi

In Romania, no provider has Alcatel certification. But Orange Romania does not usually transmit location information, while Vodafone Romania always transmits this information and can not remove it because it is a network parameter!

I suspect it can still be ignored by PBX. For example in ISDN the FacilityIE flag set to '00' ignores some causes of rejection. I have already set the BsyCausVoi flag as 'FF FF FF FF FF', but it has only effect for outgoing calls. Other undocumented flags are VOIPCaUnav and VOIPDebug. Does anyone know what these flags refer to?

Best regards

[enio.eltz]

Hi aurelian

Have you ever tried to enable the check-box P-Access-Network-Info in Gateway Parameters --> your SIP gateway --> Identity?
I have been looking for an information during a test here and seen this option.

Best regards.

[aurelian]

Hi enio,

Yes, of course I tried this check-box but it did not work for incoming calls or it is a bug.
Other types of PBXs like Panasonic NS500 or Unify OpenScape Business have no problems with this provider.
Anyway thanks for your suggestions.

Best regards,

Aurelian

[hami987]

Dear eng, add g729 codec to voip parameters-cdecs, also keep g711a,g711u and g729 it will solve.

[hami987]

Dear eng, add g729 codec to voip para-cdec it will solve.