Outgoing call failure with flowroute trunk: incoming works fine

[mongoman123]

This is odd. I have a snom one system set up on a mac mini, and I managed to get flowroute for outgoing calls setup as a trunk before.

 

Then, I havent used the system in about two weeks, and now, it appears snomone has lost the trunk - for whatever reason. While this is concerning enough,

my real problem is that I cant seem to re-establish the flowroute trunk for outgoing calls.

 

Incoming calls work fine, which tells me my registration with flowroute should be fine.

 

Outgoing calls result in a 404 error - this is my error log:

 

6] 2011/05/12 10:11:01: Sending RTP for NzNjYzMzZjg3ZDE4MDNiNzU1NjcxZGY5NzJmNGQ0MmQ. to 94.166.124.150:52356, codec not set yet

[7] 2011/05/12 10:11:01: Cannot convert number 913108904819 into global format

[7] 2011/05/12 10:11:01: Last message repeated 4 times

[7] 2011/05/12 10:11:01: set_codecs: for NzNjYzMzZjg3ZDE4MDNiNzU1NjcxZGY5NzJmNGQ0MmQ. codecs "9 8 2 3 0 18", codec_preference count 6

[7] 2011/05/12 10:11:01: Cannot convert number 913108904819 into global format

[5] 2011/05/12 10:11:01: Dialplan "STARMD": Match 913108904819@sip.starmds.com to <sip:13108904819@sip.flowroute.com;user=phone> on trunk flowroute

[1] 2011/05/12 10:11:01: UDP: TOS could not be set

[1] 2011/05/12 10:11:01: Last message repeated 2 times

[7] 2011/05/12 10:11:01: set_codecs: for b965bb9a@pbx codecs "0 3 2 9 18 8", codec_preference count 6

[6] 2011/05/12 10:11:01: Codec gsm/8000 is chosen for call id NzNjYzMzZjg3ZDE4MDNiNzU1NjcxZGY5NzJmNGQ0MmQ.

[7] 2011/05/12 10:11:03: Call b965bb9a@pbx: Clear last INVITE

[5] 2011/05/12 10:11:03: INVITE Response 404 Not Found: Terminate b965bb9a@pbx

[3] 2011/05/12 10:11:03: Via is empty, cannot send reply

 

What on earth am I doing wrong?

 

Any help is really appreciated...

 

Thanks!

[katerina]

Hi,

 

Can you enable SIP Logging, set log level to 7, and post the log here so we can see more details?

[koolandrew]

It appears that there are several issues. It would be help to have your dialplan and trunk config as well, but i would make sure that your provider will accept the terminating number preceeded by a 9. I believe that if you remove this, it will a good start although that is not clear as you may have this trunk set to be a global trunk and that could another issue. Moreover, it appears you are using gsm, and very few sip carriers will support that codec.

 

It appears it might be more than one thing.

[Vodia PBX]

MAny providers have a problem with the RFC3325 presentation that we are doing-. Try the settings "No Indication" in the trunk settungs and see if that solves the problem.

[lerman]

My snomONE flowroute trunk has developed the same problem. It started yesterday for now apparent reason. Incoming calls work fine. Outgoing calls don't seem to work. Incoming calls DO work.

 

Log level 7 is attached.

 

Registration seems to be failing, but I have no idea why.

 

Ken

 

 

 

snom.log.txt

[pbx support]

It is not the same problem. In your case, the none of the messages are reaching "216.115.69.144". So this is either network issue or DNS issue resolving to the wrong address.

[lerman]

It is not the same problem. In your case, the none of the messages are reaching "216.115.69.144". So this is either network issue or DNS issue resolving to the wrong address.

Thanks for the prompt reply. I can ping sip.flowroute.com (216.115.69.144), and can traceroute to it. I can do a telnet sip.flowroute.com 5060.

 

What in the log tells you that the messages are not reaching that address? Is it that there are no responses?

 

Regards,

 

Ken

[pbx support]

What in the log tells you that the messages are not reaching that address? Is it that there are no responses?

 

If you see "Tr" in the log message, that means PBX is repeating the same message again because it did not receive any response.

 

[5] 20120822130040: SIP Tr udp:216.115.69.144:5060:
INVITE sip:12034267166@sip.flowroute.com;user=phone SIP/2.0

 

If this was a working system and suddenly stopped (without any software upgrade), then it is generally something outside the software causing it. Could be external firewall or if the system was rebooted, then sometimes system firewall can cause this.