MESSAGE_SEND_STATUS gives SUCCESS when the registered device goes offline

I am using the below dialplan for messaging .

exten => _XX.,1,MessageSend(pjsip:${EXTEN})
exten => _XX.,n,NoOp(Message body: ${MESSAGE(body)})
exten => _XX.,n,NoOp(Message send status:${MESSAGE_SEND_STATUS})
exten => _XX.,n,Hangup()

But it’s showing Message_send_status as Success even when the device goes offline due to abrupt disconnection of network.
Executing [XXXX@message:1] MessageSend(“Message/ast_msg_queue”, “pjsip:XXXX”) in new stack
WARNING[22771]: res_pjsip_messaging.c:719 update_to_uri: To address ‘XXXX@XX.XX.X.XX’ is not a valid SIP/SIPS URI
– Executing [XXXX@message:2] NoOp(“Message/ast_msg_queue”, “Message body: Testing for offline”) in new stack
– Executing [XXXX@message:3] NoOp(“Message/ast_msg_queue”, “Message send status:SUCCESS”) in new stack
– Executing [XXXX@message:4] Hangup(“Message/ast_msg_queue”, “”) in new stack
== Spawn extension (message, XXXX, 4) exited non-zero on ‘Message/ast_msg_queue’

Is there any possible way to handle the device state when its network goes down before it’s qualify frequency.
This makes the dialplan to dial or send message, but the other is not reachable.

Is there any possible way to send qualify through dialplan ?

No, it is not possible to do either in the dialplan.

Thank you

Is there any configuration to handle this?

There is no configuration. The SIP MESSAGE request goes out and is retransmitted, there is nothing at that point in the dialplan. Waiting in the dialplan would also be bad if such a thing were implemented, since it would block all other messages. It’s not designed for the scenario you’re referring to currently.

OK, Thanks for the response

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.