[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Yu Boot <yu@y...>
 Subject :  Re: [yate] accfile uplink, no callerID
 Date :  Sun, 01 Feb 2015 18:47:54 +0300
Anyone? Here's some more info about this problem:

yate cdr:
1422790927  1412359566-229593       sip/446327      195.211.120.9:9060   
  014716  0000007 0       5       5       incoming  ringing Request 
Terminated
1422790927  1412359566-229593       sip/446328      10.0.37.10:5060 
014716  0000007 0       5       5       outgoing  ringing Cancelled



incoming Wireshark SIP dump  http://pastebin.com/LvzFk0Xq
outgoing Wireshark SIP dump http://pastebin.com/ymbLqsLy


Help me please with this callerID problem!

29.01.2015 17:22, Yu Boot пишет:
> When receiving incoming call from password-protected (accfile.conf) 
> SIP trunk, other end (regfile client) don't see any callerID, looks 
> like Yate just cut it out.
>
> The only way to mitigate this problem is to ask SIP provider to copy 
> callerid to callername variable, and then copy it back before our Yate 
> routes call out. But this is impossible sometimes. How to make Yate to 
> just pass callerID from accfile trunks without these tricks?
>
>
> accfile.conf:
> [trunk1]
> enabled=yes
> protocol=sip
> formats=alaw
> registrar=1.X.X.X:9060
> outbound=1.X.X.X:9060
> interval=180
> username=014716
> authname=014716
> password=XXXXXXXXXX
>
> regexroute.conf:
> [to_client1]
> .*$=return;called=0000007;
>
> regfile.conf:
> [0000007]
> password=XXXXXX





  
    
  
  
    
Anyone? Here's some more info about this problem:

yate cdr:
1422790927      1412359566-229593       sip/446327      195.211.120.9:9060      014716  0000007 0       5       5       incoming        ringing Request Terminated
1422790927      1412359566-229593       sip/446328      10.0.37.10:5060 014716  0000007 0       5       5       outgoing        ringing Cancelled



incoming Wireshark SIP dump  http://pastebin.com/LvzFk0Xq
outgoing Wireshark SIP dump http://pastebin.com/ymbLqsLy


Help me please with this callerID problem!

29.01.2015 17:22, Yu Boot пишет:
When receiving incoming call from password-protected (accfile.conf) SIP trunk, other end (regfile client) don't see any callerID, looks like Yate just cut it out.

The only way to mitigate this problem is to ask SIP provider to copy callerid to callername variable, and then copy it back before our Yate routes call out. But this is impossible sometimes. How to make Yate to just pass callerID from accfile trunks without these tricks?


accfile.conf:
[trunk1]
enabled=yes
protocol=sip
formats=alaw
registrar=1.X.X.X:9060
outbound=1.X.X.X:9060
interval=180
username=014716
authname=014716
password=XXXXXXXXXX

regexroute.conf:
[to_client1]
.*$=return;called=0000007;

regfile.conf:
[0000007]
password=XXXXXX