Derfloh, I can't see how that can be the case. All handsets are fine and then suddenly al handsets start having the problem. I've been through and number withheld not activated.
noticed that when outbound fails, it affects all handsets for a specific time period. I checked logs and noticed failed calls had this set:
Pres=Restricted (1)
How do I get past this? Could it be adding an A to the shortcode to force calls to be non-restricted?
Thanks,
SW
After 6 days of settled activity, this problem has returned. Looks like it's the realm field. I really need to work out how to hard configure this to remain static. Any ideas?
09:39:51 3130593128mS SIP Tx: UDP 192.168.1.249:5060 -> y.y.y.y:5060
INVITE...
Hi,
Please see the engineering doc from the SIP provider. Still struggling to get the fields correct.
Thanks,
Alhttps://files.engineering.com/getfile.aspx?folder=e934cdb8-e4d2-41a1-b261-472d384adeed&file=CFHF-SIPTrunkingTechnicalSpecification-130121-0853-1468.pdf
I've spoken to the provider and it's definitely the realm field causing problems. Which settings in IPO can allows me to update this or at least alleviate the problem?
critchey, checked and numbers not set to withheld.
Here is a longer set of output. Update is that this happens in spikes and affects a group of outbound attempts.
Called[9] Type=Default (100) Reason=CMDRdirect Keypad[9]
14:03:28 1850295718mS CMMap: a=0.0 b=0.0 pcp[932]b0r1 RTPD0
14:03:28...
Hi Critchey, No it's the IPO system sending the 405. I checked with the provider and Message, register, subscribe, publish are missing from the IPO method list. As you can appreciate, it's been a tough one to nail down.
Just wondering if the association method plays a part and if it does for a...
Hi,
Still been having an odd experience with this one. I made the changes to the ARS form and I thought that the anonymous.invalid from field problem had gone. The customer has reported intermittent bouts of this so I started looking at monitor trace again. Please see redacted output below. We...
Thanks Janni78 and Critchey. I don't have the anonymous box checked and SIP trunk was set to use internal data. I'm going to try Janni78's suggestion of using ITSP domain info and removing the @example.com from ARS short code.
Just to clarify, if i set ITSDP domain to example.com is this ok...
Hi,
This is first time I've had to ask for help so be gentle. We have configured a registered SIP trunk but are intermittently sending out calls with anonymous@anonymous.invalid in the from field as well as anonymous.invalid in the realm field interchangeably. I can't for the life of me figure...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.