Sip user call is failing every now and then

[Bigsin]

Sip user call is failing every now and then

Sipuser: 200 registred on MBG is dialing 123456789
We discovered when it's failing the MiVoice Business is checking 123456789 in the "SIP Peer Profile Assignment by Incoming DID"
When I add 1* to "SIP Peer Profile Assignment by Incoming DID" with proper SiIP Peer configuration it will never fail again.
But the MiVoice should not checking this form for calls from SIP users.
This is also not a solution/workaround because it will conflict with DID numbers.

Pcap trace in MBG untill the 404 is exactly the same for a succesfull or failed call.

Any thoughts?

Bigsin

 

[Billz66]

can you clairify what you are saying

are you saying there is a SIP teleworker ext 200 making an outgoing call to 123456789
(assume thats a made up number ) but that 1 is an ars access code ?

and the user is making an outgoing call via a MIVB and that the number they are dialling IS not one of the numbers that belongs to the SIP trunk being used for the outgoing call?


If I never did anything I'd never done before , I'd never do anything.....

 

[Bigsin]

Yes 123456789 is a made up number.
The number is routed via Ars to a sip trunk.
Ars is not an issue. This is setup correct.


The call is routed (sometimes)in the MIVB via "SIP Peer Profile Assignment by Incoming DID" instead of handled as a call from a sip teleworker user.

We had 1* programmed in this form to a sip peer.
The number will be incorrect modified by the "inward dialing modification off the sip peer.
Result failing call setup.

If we delete 1* out of the "SIP Peer Profile Assignment by Incoming DID" the call is rejected because there is no match in this form.

I think 50% of nu testcalls to 123456689 are failing.

In case 1* is programmed in the SIP Peer Profile Assignment by Incoming DID ccs tracé is showing an incoming call from sip peer xyz

This is strange because the call is setup by a sip user.