Author Topic: Question about Asterisk tickets  (Read 6907 times)

maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Question about Asterisk tickets
« on: December 07, 2012, 07:13:55 pm »
I noticed l3mce saying that there are only a few open tickets left for 10.04. So I wondered a little, because I remember a ticket for Asterisk for example, where no telephonenumbers show up for incoming calls.
I keep my system up to date, but I still have this issue (aside not being able to call to outside of the coutnry and mythtv constantly crashing) my only standing issue.
So is this fixed and if so, how can I get it to work here?

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3020
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: Question about Asterisk tickets
« Reply #1 on: December 07, 2012, 09:15:31 pm »
The ticket was closed as the original creator of the ticket did not answer questions, and others have working CLI

maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #2 on: December 08, 2012, 10:12:02 am »
so, do you think installing from scratch might change things for me?

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #3 on: December 08, 2012, 01:54:11 pm »
i have the incoming numbers work, and maybe i can help you identify your problem .
please describe how you setup your lines


maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #4 on: December 08, 2012, 03:28:29 pm »
my setup is pretty straight forward:
I have a internetrouter (AVM Fritz!Box) that also receives all incoming calls. I registered asterisk via webadmin as a IP-Phone and thats it.
Since I was unable to make international calls, I hooked up another IP-Phone directly to the box, bypassing lmce- and I can call anywhere in the world and see the incoming phone-number.
The only other thing I did, was the dial-out prefix in lmce is "0".

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #5 on: December 09, 2012, 01:59:29 pm »
you can check if the box send  caller id via sip-info or  p-asserted-id

and send  asterisk log for incoming call

maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #6 on: December 10, 2012, 08:07:23 pm »
thanks for the help...I will check this, when I find the time and report back

maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #7 on: December 16, 2012, 10:56:51 am »
Sorry for taking so long to reply...but its a busy time for me right now.
Anyways, I checked Asterisk.log when I called my line from my cellphone and this here is all I could find so far:
Quote
05   12/16/12 10:41:22.883      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/204@trusted-43d3;1, callerid  <0xb62feb70>
05   12/16/12 10:41:22.924      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/200@trusted-feff;1, callerid  <0xb62feb70>
05   12/16/12 10:41:22.965      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/201@trusted-1046;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.021      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/206@trusted-0b67;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.062      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/203@trusted-58ba;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.103      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/202@trusted-e373;1, callerid  <0xb62feb70>
05   12/16/12 10:41:25.097      NotifyHangup channel Local/202@trusted-e373;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.107      NotifyHangup channel Local/203@trusted-58ba;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.118      NotifyHangup channel Local/206@trusted-0b67;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.128      NotifyHangup channel Local/201@trusted-1046;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.139      NotifyHangup channel Local/200@trusted-feff;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.149      NotifyHangup channel Local/204@trusted-43d3;1, reason Unknown <0xb62feb70>
01   12/16/12 10:41:25.159      Failed to parse channel SIP/620-0000000d <0xb62feb70>
05   12/16/12 10:41:25.170      NotifyHangup channel SIP/620-0000000d, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.180      NotifyHangup channel Local/204@trusted-43d3;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.190      NotifyHangup channel Local/202@trusted-e373;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.200      NotifyHangup channel Local/203@trusted-58ba;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.211      NotifyHangup channel Local/200@trusted-feff;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.221      NotifyHangup channel Local/201@trusted-1046;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.231      NotifyHangup channel Local/206@trusted-0b67;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:55.935      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/204@trusted-bcbf;1, callerid  <0xb62feb70>
05   12/16/12 10:41:55.985      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/200@trusted-61ca;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.026      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/201@trusted-2474;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.067      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/206@trusted-02ba;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.110      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/203@trusted-f083;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.152      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/202@trusted-a540;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.395      Ignoring event because exten is 203 is channel is Local/203@trusted-f083;2 <0xb62feb70>
01   12/16/12 10:41:56.416      Failed to parse channel Local/202@trusted-a540;2 <0xb62feb70>
01   12/16/12 10:41:56.426      Failed to parse channel Local/200@trusted-61ca;2 <0xb62feb70>
01   12/16/12 10:41:56.436      Failed to parse channel Local/201@trusted-2474;2 <0xb62feb70>
01   12/16/12 10:41:56.446      Failed to parse channel Local/206@trusted-02ba;2 <0xb62feb70>
05   12/16/12 10:41:56.467      Ignoring event because exten is 204 is channel is Local/204@trusted-bcbf;2 <0xb62feb70>
05   12/16/12 10:41:56.507      NotifyHangup channel Local/202@trusted-a540;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.518      NotifyHangup channel Local/201@trusted-2474;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.538      NotifyHangup channel Local/206@trusted-02ba;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.548      NotifyHangup channel Local/206@trusted-02ba;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.559      NotifyHangup channel Local/202@trusted-a540;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.579      NotifyHangup channel Local/200@trusted-61ca;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.590      NotifyHangup channel Local/201@trusted-2474;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.600      NotifyHangup channel Local/200@trusted-61ca;2, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.129      NotifyHangup channel Local/203@trusted-f083;1, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.139      NotifyHangup channel Local/204@trusted-bcbf;1, reason Unknown <0xb62feb70>
01   12/16/12 10:42:02.150      Failed to parse channel SIP/620-0000000e <0xb62feb70>
05   12/16/12 10:42:02.160      NotifyHangup channel SIP/203-0000000f, reason Normal Clearing <0xb62feb70>
01   12/16/12 10:42:02.170      Failed to parse channel Local/203@trusted-f083;2 <0xb62feb70>
05   12/16/12 10:42:02.180      NotifyHangup channel SIP/204-00000010, reason Normal Clearing <0xb62feb70>
01   12/16/12 10:42:02.190      Failed to parse channel Local/204@trusted-bcbf;2 <0xb62feb70>
05   12/16/12 10:42:02.200      NotifyHangup channel SIP/620-0000000e, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.211      NotifyHangup channel Local/204@trusted-bcbf;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:42:02.221      NotifyHangup channel Local/203@trusted-f083;2, reason Normal Clearing <0xb62feb70>

The interesting part is, that I have another sipphone hooked to the fritzbox parallel to LMCE, but there I get callerid shown, so clearly the box is sending them. Unfortunately I was so far unsuccessful in finding out how it is sending them.

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #8 on: December 16, 2012, 02:29:42 pm »
Maverick

That is not what i need. Here is how to collect the needed logs: launch asterisk -r from your core type: core set debug 0 type: core set verbose 999999

And then make an incoming call from your landline.


maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #9 on: December 16, 2012, 03:48:55 pm »
I did as you suggested....I attached the log from the call I made...I hope I got it all

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #10 on: December 16, 2012, 05:30:32 pm »
from your  log i can see any sip info  about call .

please  try to enable  sip debug

asterisk -r 

sip set debug on
core set verbose 999999
 and post log again

maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #11 on: December 16, 2012, 06:49:02 pm »
here you go

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #12 on: December 16, 2012, 08:26:48 pm »
ok now i can see .


the number 015253968856

is you CID ?


maverick0815

  • Addicted
  • *
  • Posts: 546
    • View Profile
Re: Question about Asterisk tickets
« Reply #13 on: December 16, 2012, 09:29:23 pm »
my cellphone

cfernandes

  • Guru
  • ****
  • Posts: 290
    • View Profile
    • my company web site
Re: Question about Asterisk tickets
« Reply #14 on: December 16, 2012, 09:53:56 pm »
ok

make a backup of file  /usr/pluto/bin/db_phone_config.sh  

and use the new one i have attached .
change permission to 777   and run  the script .

that try to  call  and verify that linuxmce  show correct CID
« Last Edit: December 17, 2012, 12:11:06 pm by cfernandes »