11-20-2014 03:08 AM - edited 03-21-2019 10:21 AM
11-24-2014 03:46 AM
mmm...anyone please help
11-24-2014 04:09 AM
I have no access to SPA8000, but we may try it.
Return SIP Timer Values to default. Turn syslog&debug (highest level) and send them to 192.168.250.250. Catch all packets from/to affected device using a packet tracer, like Wireshark, tcpdump or so.
This trace will help us to analyze the issue.
Note that trace may contain calling and called numbers as well as other sensitive information.
12-08-2014 09:43 PM
The problem disappear if I set all the lines "Trunk Group:none".
But I really need the trunk group service, any idea?
Thank you Dan Lukes, I'm very new in VoiP, too technically I may not able to follow.
12-09-2014 02:04 AM
Particular name/password pair should be used on either one line (Ln) or one trunk (Tn) only unless your Telco allow simultaneous logins. The call may be terminated whenever SIP registration from second source will arrive if simultaneous logins are not allowed. Did you configured particular name/password pair twice ?
What's the value of the "Contact list" option related to hunt group you assigned to lines ? Did you followed the documentation ?
Note that I never seen a SPA8000 (and you are unable to provide details/logs in advance) so I'm guessing only.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide