No Reponse to VM SUBSCRIBE message?
OK, quick background...
VM is working for me - calls get fowarded to VM on no answer by the SPA, and I get VMWI and stutter tone MWI when there's a VM. All Good. :) However, I noticed a fair amount of traffic, and a significant excess of outgoing SIP messages to incoming SIP messages, so I thought i'd throw a syslogger at the problem. What appears to be happening is that the SPA is trying to subscribe to VM, but getting no response to the subscribes. It sends 15 subscribes (or thereabouts) over 60 seconds, then waits 30 seconds before trying again. I imagine the voxalot servers don't appreciate this. However, usually in the middle of all this, voxalot nicely sends a notify - which the SPA acks. Have I stuffed up my SPA settings to cause this, or should voxalat be acking the subscribes? Is the problem that the call id in my sub requests is an internal IP addy (192.168.1.3) or is that a red herring? PM for account details if you want to debug - I've removed them from the syslog data. Code:
[0:5060]->71.13.117.133:5060 Then, in the middle I get: Code:
[0:5060]<<71.13.117.133:5060 Code:
[0:5060]->71.13.117.133:5060 Code:
[0:5060]->71.13.117.133:5060 Then issues this message Code:
[0]SUBS:Failed(55). Retry in 30s |
Thanks for the detail. If I recall correctly (I will check a bit later as I am currently offsite) the responses to the SUBSCRIBES are not immediate.
Let us look at this tonight (after the server move) and I will respond with our findings. |
Quote:
I'll probably still be working till around 22:00EST so feel free to get in touch... |
Just some more info
I syslogged the messages from a hard reboot, and noticed the following:
Code:
[0:5060]->71.13.117.133:5060 Code:
[0:5060]<<71.13.117.133:5060 Code:
[0:5060]->71.13.117.133:5060 |
Quote:
I just modified the SUBSCRIBE logic to return a 200 OK. The NOTIFY will still take up to 60secs to send after the 200 but let's see if the 200 at least keeps the ATA happy. |
Magic:
[0]SubOK. NextSub in 599 (1) My expires is currently set to 600. I'll bump it up to 43200 (12 hours). |
Great!
Thanks again for the diagnostics. Certainly makes it easier for us to turn around the fixes. |
All times are GMT. The time now is 11:10 PM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.