1b.app
Link copied -

Doesn't process cellee parameter in call making API

Doesn't process cellee parameter in call making API
Boxing http://crm.sportlife.ua/
Test contact http://crm.sportlife.ua/admin/shop/users/659/
1. Outgoing call from the office by mouse click, a request is made to the PBX via AMI, the call occurs:
a call to the opera, the opera picks up the phone
http://crm.sportlife.ua/api/registercall/?&channel=SIP/1502121-0000008b&...
then there is a connection to the client number + the client card is opened
the client picked up the phone, there was a conversation, the end of the call
http://crm.sportlife.ua/api/registercall/?&channel=SIP/1502121-0000008b&... -44-36-1502121-0638432084.wav
client card closed
there is only one entry in the call report, but the fields to whom the call is made are empty, this is due to the fact that it does not pull up the
Original question is available on version: ru

Answers:


Andrey wrote:
Doesn't process cellee parameter in call making API

probably because the right parameter is written as callee ???
)))
where did you get cellee i don't know))
05.02.2021, 10:11
Original comment available on version: ru


Ustimenko Igor
OneBox CTO wrote:
where did you get cellee i don't know))

This is indicated in the documentation example https://prnt.sc/yerhdh
05.02.2021, 17:28
https://qube-soft.com/ crm erp onebox qubesoft внедрение аналитика 1с интегратор Original comment available on version: ru


Ustimenko Igor
OneBox CTO wrote:

Andrey wrote:
Doesn't process cellee parameter in call making API

probably because the right parameter is written as callee ???
)))
where did you get cellee i don't know))

I agree on outgoing there was a typo, did not finish watching. I double-checked the correct code on the input, the garbage is pouring
06.02.2021, 15:39
Original comment available on version: ru


Andrey wrote:

Ustimenko Igor
OneBox CTO wrote:

Andrey wrote:
Doesn't process cellee parameter in call making API

probably because the right parameter is written as callee ???
)))
where did you get cellee i don't know))

I agree on outgoing there was a typo, did not finish watching. I double-checked the correct code on the input, the garbage is pouring

well, according to your * it pours all the numbers that it found
it’s not clear why you put it at all if there is a number to which the call is going
06.02.2021, 15:44
Original comment available on version: ru


Ustimenko Igor
OneBox CTO wrote:

Andrey wrote:

Ustimenko Igor
OneBox CTO wrote:

Andrey wrote:
Doesn't process cellee parameter in call making API

probably because the right parameter is written as callee ???
)))
where did you get cellee i don't know))

I agree on outgoing there was a typo, did not finish watching. I double-checked the correct code on the input, the garbage is pouring

well, according to your * it pours all the numbers that it found
it’s not clear why you put it at all if there is a number to which the call is going

The API documentation for Creating calls says: "Callee - If you do not specify anything here, the system will substitute default numbers here for an incoming call" Therefore, it appears that calle can take precedence over the setting in integration.
07.02.2021, 10:46
Original comment available on version: ru


Andrey wrote:
The API documentation for Creating calls says: "Callee - If you do not specify anything here, the system will substitute default numbers here for an incoming call" Therefore, it appears that calle can take precedence over the setting in integration.

"From this comes up that calle can take precedence over the setting in the integration." - This phrase of yours does not allow me to understand the essence of the issue.
07.02.2021, 17:36
Original comment available on version: ru

1 issue resolved, there was a typo in "Callee"
Question number 2 remains. Garbage in the report on calls. https://prnt.sc/yd2vwr
You write that this is because * in the telephony setting is specified in the "Numbers to which the incoming call is shown first" setting
We tested it, and if you remove * in the settings, the card does not pop up at all.
And about the comment above, I'll paraphrase: "If we create an api call, shouldn't "callee" take precedence over the "Numbers to show incoming calls first" setting???
Because the description of "API creation of calls" states that if you do not specify calle , then the system will substitute default numbers here for an incoming call https://prnt.sc/yphkyw
08.02.2021, 14:29
Original comment available on version: ru


Andrey wrote:
1 issue resolved, there was a typo in "Callee"
Question number 2 remains. Garbage in the report on calls. https://prnt.sc/yd2vwr
You write that this is because * in the telephony setting is specified in the "Numbers to which the incoming call is shown first" setting
We tested it, and if you remove * in the settings, the card does not pop up at all.
And about the comment above, I'll paraphrase: "If we create an api call, shouldn't "callee" take precedence over the "Numbers to show incoming calls first" setting???
Because the description of "API creation of calls" states that if you do not specify calle , then the system will substitute default numbers here for an incoming call https://prnt.sc/yphkyw

give an example request
08.02.2021, 14:55
Original comment available on version: ru

Thanks for the help, the tips helped.
Everything works norms. The telephone operator stuttered.
Sorry to bother you.
08.02.2021, 15:33
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment