SIP Trunk not dialling

[davea2]

Hi

I have a situation (R10.1.0.1) with a SIP trunk where when a user dials, the dialled digits get sent to the ARS table, the SIP trunk i seized but nothing gets sent to line.
No INVITE or anything. On SSA it stays in the 'Dialling' state for -sometimes- several minutes before dropping the call and falling back to the next ARS table which dial out over ISDN no problem.

Sometime a SIP trunk call will get set up no problem.

The SIP is showing as In service at all times. I cannot work out whether or not this started after an upgrade or not as it seems to be random, reports were not consistent.

It's exactly the same whether the user dials manually or via Redial

Anyone else had this?

Cheers!

 

[janni78]

Haven't had any issues with that version.

Doesn't the Monitor trace say why it doesn't send it to the SIP trunk?

"Trying is the first step to failure..." - Homer

 

[davea2]

No, everything looks fine as below, then it just sits there doing nothing...

2018-05-29T13:07:49 3007445207mS CMARS: CMARSTargetingPending
2018-05-29T13:07:49 3007445368mS CMARS: FORM: New Gradwell SB - Received Number: 01392440852
2018-05-29T13:07:49 3007445368mS CMARS: CMARSTargetingPending
2018-05-29T13:07:54 3007449530mS CMARS: Case 1 - dial_delay_time: 4000 has expired - Resolve what we might have - Called Number: 01392440852 Addr: f157938c
2018-05-29T13:07:54 3007449530mS CMARS: FORM: New Gradwell SB - Received Number: 01392440852
2018-05-29T13:07:54 3007449531mS CMARS: FOUND A SHORT CODE - short_code: N; - Tel: ."@212.11.94.246" - Called_Party: 01392440852@212.11.94.246 - Line Group Id: 4
2018-05-29T13:07:54 3007449531mS CMARS: SetCurrentTarget: Short_Code: N; - Line_Group_ID: 4
2018-05-29T13:07:54 3007449531mS CMARS: FindActiveARSByGroupID GroupID=4 - Not Found
2018-05-29T13:07:54 3007449531mS CMTARGET: Problem with Line Id: 17 - check_DNS 0 OperationalTest: 0, IP address: 0.0.0.0
2018-05-29T13:07:54 3007449531mS CMTARGET: Group Id: 4 has NOT been found in Line: 13
2018-05-29T13:07:54 3007449533mS CMCallEvt: 0000000000000000 0.108634.0 -1 BaseEP: NEW CMEndpoint f16378d0 TOTAL NOW=5 CALL_LIST=2
2018-05-29T13:07:54 3007449535mS CMARS: ModifyCMARSTarget: Short_Code: N; - Line_Group_ID: 4 set line status to CMARS_TRYING
2018-05-29T13:07:54 3007449535mS CMARS: FOUND LINE - Line Id: 18 - using line group id: 4 (code N;, line 4) - Called Number: 01392440852@212.11.94.246 - Calling Number: 818
2018-05-29T13:07:54 3007449535mS CMARS: SEND Setup TO LINE

 

[tlpeter]

CMTARGET: Problem with Line Id: 17 - check_DNS 0 OperationalTest: 0, IP address: 0.0.0.0

This is the problem. The DNS is not working thus the provider IP is not resolved.
I have seen one time where DNS also did not work but i am not sure about the version.
It seemed to be a strange prot number being used for DNS which was blocked in the firewall.

BAZINGA!

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

 

[davea2]

Hi

hmmm, I'm not sure wht DNS would be being used here.
Line 17 is no longer used so I have deleted it. It was all set up with IP Addresses anyway..

So, now it's gone and I also added the address of our DNS server in System.
Monitor output looks different but the end result is still the same...

2018-05-29T13:26:23 3008559712mS CMARS: FORM: New Gradwell SB - Received Number: 0139244085
2018-05-29T13:26:23 3008559713mS CMARS: CMARSTargetingPending
2018-05-29T13:26:23 3008559875mS CMARS: FORM: New Gradwell SB - Received Number: 01392440852
2018-05-29T13:26:23 3008559875mS CMARS: CMARSTargetingPending
2018-05-29T13:26:24 3008560467mS H323Evt: Recv: RegistrationRequest 192.168.100.119; Extn(848), time since last RRQ-KA 55000, Endpoints registered: 22; Endpoints in registration: 0
2018-05-29T13:26:24 3008560536mS H323Evt: Recv: RegistrationRequest 192.168.100.108; Extn(818), time since last RRQ-KA 55010, Endpoints registered: 22; Endpoints in registration: 0
2018-05-29T13:26:27 3008563918mS H323Evt: Recv: RegistrationRequest 192.168.100.179; Extn(850), time since last RRQ-KA 55000, Endpoints registered: 22; Endpoints in registration: 0
2018-05-29T13:26:28 3008564309mS CMARS: Case 1 - dial_delay_time: 4000 has expired - Resolve what we might have - Called Number: 01392440852 Addr: f1579418
2018-05-29T13:26:28 3008564309mS CMARS: FORM: New Gradwell SB - Received Number: 01392440852
2018-05-29T13:26:28 3008564310mS CMARS: FOUND A SHORT CODE - short_code: N; - Tel: ."@212.11.94.246" - Called_Party: 01392440852@212.11.94.246 - Line Group Id: 4
2018-05-29T13:26:28 3008564310mS CMARS: SetCurrentTarget: Short_Code: N; - Line_Group_ID: 4
2018-05-29T13:26:28 3008564310mS CMARS: FindActiveARSByGroupID GroupID=4 - Not Found
2018-05-29T13:26:28 3008564310mS CMTARGET: Group Id: 4 has NOT been found in Line: 13
2018-05-29T13:26:28 3008564311mS CMCallEvt: 0000000000000000 0.108743.0 -1 BaseEP: NEW CMEndpoint f164c06c TOTAL NOW=3 CALL_LIST=1
2018-05-29T13:26:28 3008564315mS CMARS: ModifyCMARSTarget: Short_Code: N; - Line_Group_ID: 4 set line status to CMARS_TRYING
2018-05-29T13:26:28 3008564315mS CMARS: FOUND LINE - Line Id: 18 - using line group id: 4 (code N;, line 4) - Called Number: 01392440852@212.11.94.246 - Calling Number: 818
2018-05-29T13:26:28 3008564315mS CMARS: SEND Setup TO LINE
2018-05-29T13:26:28 3008564315mS CMCallEvt: c0a864320001a8c7 18.108743.0 24558 SIPTrunk Endpoint: StateChange: END=child CMCSIdle->CMCSOffering
2018-05-29T13:26:28 3008564824mS H323Evt: Recv: RegistrationRequest 192.168.100.100; Extn(842), time since last RRQ-KA 55000, Endpoints registered: 22; Endpoints in registration: 0
2018-05-29T13:26:28 3008564853mS H323Evt: Recv: RegistrationRequest 192.168.100.150; Extn(836), time since last RRQ-KA 55000, Endpoints registered: 22; Endpoints in registration: 0
2018-05-29T13:26:31 3008567484mS H323Evt: Recv: RegistrationRequest 192.168.100.129; Extn(860), time since last RRQ-KA 55000, Endpoints registered: 22; Endpoints in registration: 0

 

[janni78]

So is Line 18 your SIP trunk?

"Trying is the first step to failure..." - Homer

 

[davea2]

Yes it is

 

[janni78]

Do you have SIP Tx, Rx enabled in Monitor? =)
It says that it's offering the call to the SIP trunk so I would assume it sends a SIP INVITE.

How is the URI it should be using configured?

I wouldn't use the "@212.11.94.246" part in the shortcode as it shouldn't be needed in later version and breaks things but that shouldn't be causing this.

"Trying is the first step to failure..." - Homer

 

[davea2]

Yep, SIP Rx and TX are enabled There's just no output

The "@212.11.94.246" is not in any shortcode having checked system, users and user rights.

The URI is set to use Intternal data, no Credentials and auth is by IP address

Really scratching my head on this one!

 

[janni78]

FOUND A SHORT CODE - short_code: N; - Tel: ."@212.11.94.246"

Looks like it's in the "New Gradwell SB" ARS.

"Trying is the first step to failure..." - Homer

 

[DanACS]

Silly question but have you got an IP route? Had the same symptoms when I got used to installing via an SBC then did one without and missed the IP route.

ACSS - SME
APSS - SME
APDS - Unified Communications
ACS - IP Telephony
ACA - IP Telephony

 

[davea2]

Janni

We surely need the "@212.11.94.246" bit in there somewhere?
Always has been before and this system has had that ARS table since R7.0 - is this now not required?
To my knowledge our engineers ar still doing that but without issue

Dan - yep I've even added a default route whilst we try to sort this