Jump to content
KAZOOcon: hackathon signup and details here! ×

Matrixdz2002

Members
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Matrixdz2002

  1. Hi there, I've several Kazoo accounts, some use a sip trunk (PBX Connector) while other use Kazoo SmartPBX. Since last month I have issue with gathering the call logs. I'm trying to download the call logs for a specific period June (06/01/2023 to 06/30/2023) but I always have empty result, while if I set the period for April or May, or even July I can get the call logs history For some other accounts, I can see only see some call logs (06/01/2023 to 06/10/2023) but not the whole month (06/01/2023 to 06/30/2023) When I checked on Bigcouch, I can see that there is a document account/xx/xx/xxxxxxxxxxxxxxxxxxxxxxxxxx-202306 and inside I can see a document for each calls (inbound or outbound) I also tried with CDR API and have the same results. After some troubleshooting, I decided to reboot the server which fixed the issue for some accounts, but still have 3 accounts that still can't gather only some call logs (06/01/2023 to 06/10/2023) Did someone had the same issue and was able to fix it? Or do you have any idea what can cause the issue? Thanks,
  2. Hi there, I have a SIP trunk (offnet) configured for outbound calls. I want to configure it in a way, when I have local outbound calls (Belgium) to send local DID (0123456789) and when the call is an international one, I want it to send e.164 format +32123456789 For information, Belgian DID are: 9 digits for Fixed DID (including zero) 10 digits for Mobile DID (including zero) I configured the offnet as following: "formatters": { "request": [ { "regex": "^(\\d{9,10})$", "prefix": "" } ], "caller_id_number": [ { "regex": "^(\\d{9,10})$", "prefix": "+32" } But when I make a call, the caller ID sent is always local one 0123456789 rather than sending +32123456789. I guess, I'm missing another settings but couldn't find where and which one. Can you please advise what should be set for sending e.164 format when making international call? Regards,
  3. Hello to the great community, Hope doing well. Now that I have a working Kazoo and outgoing calls based on destination. I would like to apply a rule to route some calls through specific SIP trunk (offnet/ressources) Below the need:I would like to apply a rule that will check the Called ID, if it's fixed number or mobile number and based on that, the call will be routed to Trunk A or B. The scenario is for Belgium. Please note: 1. Most of the callers will NOT dial the prefix +32 (they will dial 0x xxx xx xx) 2. For Belgium, the (Landlines in Liège have numbers starting with 04, and so do mobile phones all over the country. But mobile numbers are 04xx xx xx xx – 10 digits in total – while Liège numbers are 04 xxx xx xx – 9 digits in total. Liège also never starts with 04 6x, 04 7x, 04 8x or 04 9x ) Based on that: - If I call 02 xxx xx xx (Fix number), the call will be routed through TRUNK A - If I call 04 xxx xx xx (Fix Number), the call will be routed through TRUNK A - If I call 04xx xx xx xx (Mobile Number), the call will be routed through TRUNK B Adding to that the VoIP Provider requests always to send the number on E.164 format (ie. adding the prefix +32) so I need to apply it on the offnet doc Voilà, hope as usual someone can help Best Regards,
  4. Hi all, Just to let you know that after checking and monitoring the calls with diversion header enabled, I can find who is calling (Caller Originator) even the caller ID is what I set on Custom SIP header. To resume, here what I set on my Kazzo/BigCouch: - Adding "custom_sip_headers" settings to the resources doc (as per @tomas_ recommendation) - Setting "should_add_diversion_header": "true" to system_config -> Kazoo_endpoint (as per @mc_ recommendation) - On monster-ui, I enabled "Call Forwarding" and set "Keep Original Caller-ID" checked on all concerned users This way all call are correctly forwarded to the carrier and the latter is routing the calls without issue. I would like to thank each of you who assisted me on that issue. Best Regards,
  5. Hello all, @tomas_, Thanks for your reply. I tried it and the carrier accepted the call, but since I specified a number (+33123456789) on the diversion, all outgoing calls are under that number "+33123456789" "custom_sip_headers": { "Diversion": "<sip:+33123456789@sip.provider.com>;reason=unconditional" }, But in my case, I have several users where everyone has his own number (for example: +33111111111, +33122222222, +33133333333) and each forward the calls to another number Example: UserA: +33111111111 --> Forward to --> +33 6 78 00 00 00 UserB: +33122222222 --> Forward to --> +33 6 49 11 88 88 UserC: +33133333333 --> Forward to --> +33 6 41 10 10 10 What I'm looking for is how to set the correct configuration that can replace the "<sip:+33xxxxxxxxx@sip.provider.com> by the correct number of each user: <sip:UserA_number@sip.provider.com>, <sip:UserB_number@sip.provider.com>, <sip:UserC_number@sip.provider.com> For the moment, What I did is: - Deleting "custom_sip_headers" settings from the resources doc - Setting "should_add_diversion_header": "true" to system_config -> Kazoo_endpoint - On monster-ui, all users that have "Call Forwarding" enabled, have "Keep Original Caller-ID" checked With these setting, calls are forwarded and accepted by the carrier, but what I noticed is, all tested incoming calls from +33 xxxx are correctly working, while any call coming from other prefixes like +44, +32... is rejected Below example calls Scenario 1 (Working): Caller ID: +33 6 35 00 00 00 (French Mobile) Called ID: +33 1 11 11 11 11 Forwarded to: +33 6 78 00 00 00(French Mobile) But when I try to call from +32 xxxxx number to the SAME number the call is rejected with message error "503 Service Unavailable" Scenario 2 (Not working): Caller ID: + 32 2 33 12 345 (Belgian DID) Called ID: +33 1 11 11 11 11 Forwarded to: +33 6 78 00 00 00(French Mobile) I also noticed on the PCAP that on Scenario 1 , that diversion is applied and I see the Called ID, while on Scenario 2 the diversion is not applied, which led the carrier to reject the call. I still didn't figure out why it's happening. The only possible solution for me now is to use /force again custom_sip_headers, but only if I can assign the correct called ID on the Diversion (ie. <sip:UserA_number@sip.provider.com>, <sip:UserB_number@sip.provider.com>, <sip:UserC_number@sip.provider.com> ) Best Regards,
  6. Hi @mc_ , Thank you for the support. Unfortunately I still can't apply the diversion header I applied on kazoo_endpoints (cf. below): { "_id": "kazoo_endpoint", "_rev": "17-85c7845s62ca8b0dec9fed889ef5c6661", "default": { "should_add_diversion_header": "true", "default_ignore_completed_elsewhere": true, "restrict_to_known_types": false } } +++++++++ Below information of the resources: { "_id": "ad9850e6484b13b3e54781a210dffbb2", "_rev": "71-72b87146c01e1dd9547bf7f2b47e94133", "pvt_type": "resource", "name": "Carrier Test FR", "enabled": true, "flags": [ ], "weight_cost": 1, "rules": [ "^\\+33\\d{9,}$" ], "gateways": [ { "server": "sip.xxxxx.com", "username": "myusername", "password": "mypassword", "prefix": "", "suffix": "", "media": { "fax_option": false }, "codecs": [ "PCMA", "PCMU", "G729" ], "enabled": true } ], "grace_period": 5, "formatters": { "request": [ { "regex": "^(\\d{9,})$", "prefix": "+33", "suffix": "" } ], "diversion": [ { "match_invite_format": true, "direction": "outbound" } ] } } According to the carrier, to use a third party number, I will need to add a diversion header in the INVITE that contains a Carrier DID enabled for outbound
  7. Hi all, Thank you for your help. Indeed the "rules" regular expressions helped to set the routes conditions. I was able to route a call based on destination I will test also callflow to route based the Caller ID. Thank you all, I couldn't find it without your help :-) I take this opportunity also to ask another question regarding Call Diversion. I read on some forum that Call Diversion headers are used to support call forwarding and deflection, and also enable outbound calls from phone numbers that aren't assigned by the carrier The question is how to set the call diversion using regex to allow the below scenario: I have a caller from UK calling one of our employee/customer on his fixed line and that employee/customer has set a call forwarding to his mobile number For example: Caller ID : +44 2 11 11 11 Called ID : +33 1 23 45 67 89 FORWARD CALL TO: +33 6 78 00 00 Without a Call diversion, the call will be rejected by the carrier, so how can we fix it? Thanks
  8. Hello there, Happy to be among you. I'm testing Kazoo on premise and checked several documentation, unfortunately (for sure I'm missing something) I couldn't find how to route OUTGOING calls based on : 1. Destination 2. Caller ID Considering I have 3 SIP Trunks: a) Trunk A (Preferred for France outgoing Calls) b) Trunk B (Preferred for China outgoing Calls) c) Trunk C (Preferred for the rest of the world outgoing Calls) Below some scenarios: Scenario 1 "Destination based routing": I would like to apply a rule that will check Called ID (ie. destination) and based on that it will use Trunk A, B or C. For example: - If I call +33 xxxxxxxxx, the call will be routed through TRUNK A - If I call +86 xxxxxxxxx, the call will be routed through TRUNK B - If I call +1 or +32 or any other prefix (different from +33 and +86) the call will be routed through TRUNK C Scenario 2 "Caller ID based routing": I have 2 customers: a) Customer A: Has been assigned following block of fixed numbers: +352 412 300 to +352 412 350 b) Customer B: Has been assigned following block of fixed numbers: +34 411 111 700 to +34 411 111 730 I would like to apply a rule that will check Caller ID and based on that it will route the call through Trunk A or C. For example: - All calls made with a caller ID belonging to block of fixed numbers: +352 412 300 to +352 412 350, will be routed through TRUNK A - All calls made with a caller ID belonging to block of fixed numbers: +34 411 111 700 to +34 411 111 730, will be routed through TRUNK C Hopefully the below scenarios are clear. Please don't hesitate if you need further information/details. Thank your for your help
×
×
  • Create New...