Incoming Calls from OVH to OpenIP

[AWS2P]

Hi;
strange situation tonight, i've a Cloud amazon lightsail PBX running 3CX latest version.

This pbx has a working SIP trunk from Openip and receive also incoming calls from a OVH SIP number , in OVH manager this line is permanently forwarded to Openip sip trunk number.

This is working like this, waiting porting time to eliminate OVH at the end.

For now, when i call OVH number, i hear ring back tone but nothing is visible in "Number of calls in use" not either in "activity log" (absolutely nothing traced) when i hang up that's the weird part, call history increase 3 calls in once with exact same " from " number which is mine so it seems OVH send good number to 3CX via Openip trunk and "to" field is mobile line on which inbound rule need to forward when OOH (that's good too).



On end mobile line nothing rings.

If i call directly on Openip number, everything is ok, mobile receive call and audio both ways.

I re registred openip trunk, rebooted 3CX and do new tests with no behavior change. I suspect OVH forwarding, but for now i have no access to this settings, customer only has.

If I force OH with *641 , then incoming OVH calls are working and forward to external number works. Might be a restriction on OVH side? or what can change on 3CX side when in OOH?

what do you think about this ?

 

[StefanW]

Hi,

the ringback tone might be generated by the Provider and not 3CX. Have you checked with Wireshark if you get an Invite from OpenIP? It might be that the invite is different since the call is forwarded and does not match the trunk settings in this case. But lets start with a pcap and review the invite data.

 

[AWS2P]

the ringback tone might be generated by the Provider and not 3CX. Have you checked with Wireshark if you get an Invite from OpenIP? It might be that the invite is different since the call is forwarded and does not match the trunk settings in this case. But lets start with a pcap and review the invite data.

Why same settings works when PBX is in OH? if invite is wrong should be wrong all the time no ? not only when PBX is in OOH.

 

[JohnS_3CX]

Hi aws2p

Trace the call in a capture, see what comes in and from where

 

[AWS2P]

My feeling is about an OVH restriction concerning the direct abutment of the 2 sections of call

 

[AWS2P]

Working situation:
- PBX in OH, calls are forwarded to a Q and mobile in DNA (this works)

Not Working situation :
- PBX in OOH, calls are directly forwarded to same mobile (this works only with trunk number from OpenIp , if incoming call comes forwarded from OVH number , there's a cancel after 1 s when 3CX try to etablish a call leg to mobile

Can it be same problem as transfert on Yealink phone with SIP 302 redirect not supported?

 

[AWS2P]

For now , workaround is to let PBX in office hours all the time, client ask me to do this.