DiD what is in server activity log?

[Paddyd]

I am new to the 3CX but have worked with SIP in the past. I have an issue with direct inward dialing not working.

A remote (from me) customer has the numbers xxx 300 to xxx 399. 300 is the main line and 301 to 399 been used for DiD to extentions. As far as I can tell from the logs, all calls are all been sent to the main number of the remote 3CX ie xxx 300 even if xxx 311 ( the DiD for ext 211) is dialed. I am sure that DiD did work when first set up and the inbound rules have not been changed. I can see the calls in the log but they all appear to go the 800 group i.e. main line in.

I can not see the mention of the number the outside party dialled so can not say if a given call was sent into xxx 300 or any of the other no.s. I can not install a IP monitor as its not my network and can not just keep ring the extentions as they are guest rooms.

So by looking at the logs how would a DiD to xxx 333 look different to a call to xxx300. I think the provider is no longer sending the called number so DID can not tell the difference but from the logs can not prove it.

I accept that an IP protocol analiser (sic) would sort it out but I am not able to install one.

Any ideas gents

 

[lneblett]

It could be that the provider has changed the format of the number and the inbound rules you are using are no longer able to recognize. You can put the logger in verbose mode and likely see the numbers and react accordingly. Otherwise you will need to install wireshark or work with the provider.

Not being able to see the stream limits the ability of anyone being able to identify the problem and particularly so when apparently had worked fine in the past,

 

[Paddyd]

Thanks for the response,
It would seem that I am going to have to add a "wireshark" or the like on the net. I would have hoped that some one who uses DiD would me able to say "yes they look like ...."

Will try the verbose method but I think the 3CX is showing the results after processing. Which means a DiD which was sent to xxx300 looks just like a call which was aimed at 311 but ended up at 300!!

I will post results but still open to help

 

[lneblett]

It will show in the log, provided that the system recognizes the DID. I use them all the time and here is a snippet of a log (verbose)-

Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=1848926234
From: "Golf DID:9565900848"<sip:[email protected];nf=i>;tag=14199d54
Call-ID: ZGMxZjI5NDE2NzdkOWQ4ZTE3NDlkYjY2OWU3ZWNhMzM.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, REFER, UPDATE
Content-Type: application/sdp
Content-Length: 216

As you can see, I label each DID so I can see exactly what it is. This is done in the inbound rules. As you can see, the DID points to extension 50500.

 

[Paddyd]

Thanks so very much for that. As I do not have any successful DiD I had nothing to compare. Could I ask the meaning of

"9565900848"

I take it to be the DiD number but as it differs from a UK style number I am not 100% sure. Golf DID being the name of the rule?

I take it to be a call came into the 3CX from the outside world to 956 590 0848, this matched rule Golf DID and so was to be passed to ext 50 500. Therefore a new / internal call was made to 50500 by the 3CX

I found out just as I was leaving that only the last 6 digits of the Phone No. where being passed which explained why my inbound rules never matched. Even then the server log never showed the numbers I expected.

 

[lneblett]

your conclusion about the did number and transfer is spot on. glad I could help and hope you get yours working the way you want.

 

[Paddyd]

Got the DiD working!!!!
Below is a trace for a successful call. By success I mean I was able to see ringing current from a ATA to the Analogue handset and view the calling number. The dest No. is seen in the 3rd line down "xxx357". However the 6th line is the first in "time" 10:38:52 but it already is quoting the ext 257 internal destination. i.e. it has checked and found a valid DiD rule. Beforehand because it failed there was never a mention of the number (xxx357).
Hence I was unable to say if it was being sent, what the format was or if it had been changed by the trunk supplier.

22-Jul-2013 10:39:07.276 Leg L:462.1[Line:10000<<xxxxxxx0203] is terminated: Cause: CANCEL from xx.xx.124.76:5060

22-Jul-2013 10:38:53.010 [CM503025]: Call(C:462): Calling T:Extn:257@[Dev:sip:[email protected]:5060] for L:462.1[Line:10000<<xxxxxxx0203]

22-Jul-2013 10:38:52.969 [CM503027]: Call(C:462): From: Line:10000<<xxxxxxx0203 ("xxxxxxx0203:xxx357" <sip:[email protected]:5060>) to T:Extn:257@[Dev:sip:[email protected]:5060]

22-Jul-2013 10:38:52.969 [CM503004]: Call(C:462): Route 1: from L:462.1[Line:10000<<xxxxxxx0203] to T:Extn:257@[Dev:sip:[email protected]:5060]

22-Jul-2013 10:38:52.758 [CM503001]: Call(C:462): Incoming call from Line:10000<<xxxxxxx0203 to <sip:[email protected]:5060>


All sorted and again thanks for the help