AVAYA IPO 500V2 with ASBCE error No Subscriber Flow Matched

[Imran555]

Hi Guys
The ASBCE is configured with IPO 500v2 and registration and calls are okay
only issue i see in ASBCE is this repeated messages in incident ,
Message Dropped
Cause No Subscriber Flow Matched
Attached is screen shot for this error.

Also subscriber flow

and server flow screens shots

Any thought on above.

 

[Imran555]

Guys any help here??

 

[Ekster]

This any use?

https://documentation.avaya.com/bun..._r7.2.2/page/SIP_registration_processing.html

https://documentation.avaya.com/bun...BCE_r7.2.2/page/Subscriber_flow_matching.html

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

 

[Imran555]

well I follow the guide but still having issue,
No Subscriber Flow Matched

 

[BFG9K]

You might have your received interfaces round the wrong way.

Here's our Remote Worker flow as ref:

SBCs are black magic, so good luck

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia

 

[Imran555]

Well the Subscriber Flow is similar but issue still ressit

and i found error on monitor logs as well,
but can not figure out yet,
Traces below,

OPTIONS sip:6xxx@sipdomain.com;transport=tls;subid_ipcs=153447231 SIP/2.0
Via: SIP/2.0/TLS 172.18.80.45:5061;rport;branch=z9hG4bK0d855cff91b039ceb65fa0b7f0524e07
From: <sips:sipdomain.com>;tag=6bf633829599a0ea
To: <sips:6xxx@sipdomain.com;transport=tls;subid_ipcs=153447231>
Call-ID: 23f37d346d1686b5af34720943b1f4ad
CSeq: 1029917701 OPTIONS
Contact: <sips:172.18.80.45:5061;transport=tls>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
User-Agent: IP Office 11.1.0.1.0 build 95
Content-Length: 0

13:49:28 1743831312mS SIP Rx: TLS 172.xx.xx.xxx:13022 -> 172.xx.xx.xx:5061
SIP/2.0 403 Forbidden
From: <sips:sipdomain.com>;tag=6bf633829599a0ea
To: <sips:6xxx@sipdomain.com;transport=tls;subid_ipcs=153447231>;tag=zXcVbNmab28bf481
CSeq: 1029917701 OPTIONS
Call-ID: 23f37d346d1686b5af34720943b1f4ad
Via: SIP/2.0/TLS 172.xx.xx.xx:5061;rport;branch=z9hG4bK0d855cff91b039ceb65fa0b7f0524e07
Content-Length: 0

 

[BFG9K]

Now that I re-read this whole thread, I am realising you are seeing the same errors we are:

This is actually a known bug in SBC, and can be safely ignored. Apparently they are fixing it in a later release, this is from Avaya Support:

"This issue is about an alarm in SBCE which was caused by IPO sending SIP OPTIONS message to the remote worker user. The alarm has no service impact at all on the SBCE call processing."

You can safely ignore it for the time being.


Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia