R11 SIP bug?

[Pepp77]

Just doing an install on Powered by R11 Select using Gamma SIP trunks.

I created the SIP trunk and created a catch all incoming call route to point to my auto attendant. When I call the only number currently on the SIP trunk it fails and I get a cause 88 Incompatible destination and then a 503 service unavailable in monitor and an SSA alarm saying the following line had no incoming call route for a call and then displayed the number I called. I thought odd as surely a catchall should catch all numbers, so I amended the catch all to include the DDI (so this is the only entrant in the ICR). Called again and got the same error.

Still thinking odd I readded the catch all so I had two ICR entries, one with just a line group ID and a destination, and one with a line group ID, destination and incoming number.

Re-called the number and this time it worked as expected. If I remove either entry the calls fail!!!

Anyone else experienced this?

| ACSS SME |

 

[tlpeter]

I have something similar.
When i build 2 URI's with 0 incoming and 10 outgoing for the first and 10 incoming and 0 outgoing for the second.
Sometimes i see an error is SSA that it is trying to use the line id 10 for incoming while it does not exists.
If i then create the same ICR but then with ID 10 it works.

It seems that sometimes calls are offered on the wrong line id.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Pepp77]

My URIs are 200 incoming on both the primary and the secondary trunk (and Gamma tries both when get no response from the primary).

Outgoing is 201 on primary and 251 on secondary.

| ACSS SME |

 

[pkdev]

can you put the monitor trace on the thread to have a look ?

 

[Pepp77]

Unfortunately not for that system as I had to finish building it so the customer could use it.

I have several others coming up and I will try to replicate it on my next one and show a trace.

| ACSS SME |

 

[LJDirk]

interesting!

I have a customer in Switzerland. He has a Swisscom SIP Trunk and he can't dial Swiss numbers.
The customer dials, Invite goes out, then a little SIP Ping Pong (trying, ringing, etc) and finally Swisscom confirms with "SIP OK" the actual connection setup.
We confirm this SIP message with "ACK" and then the IP Office reports on the "CMLine Rx: v=0" a "CMReleaseComp". The cause is: "Cause 88, Incompatible destination".

If a number is dialed to Germany, everything works as expected. After the SIP OK the language path is switched through...


Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.