[Serusers] error: mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy

Charles Wang lazy.charles at gmail.com
Mon Mar 14 17:20:11 CET 2005


Still in condition. Help me please.

Best Regards
Charles


On Tue, 22 Feb 2005 01:21:44 +0800, Charles Wang <lazy.charles at gmail.com> wrote:
> Dear Paul:
> 
> Yes, I have study the readme, and both start daemon of mediaproxy
> Python server and start my ser with mediaproxy module supported.
> 
> I guess that my setting done. And I wanna forward a noanswer call from
> UA(1011) to PSTN(0939749xxx) via UA(1033).
> 
> In my log, the call is ringing from UA1011 to UA1033 first.
> Then after a few seconds, failure_route[1] trigger, and it shall be
> forward(busy) to a PSTN number.
> I define this number at usr_preferences table and attribute:fwdbusy,
> value:sip:0939749xxx at ser.xxx.net.tw.
> 
> I can find it try to connect to my CISCO trunk (xxx.xxx.190.243), but
> why is its uri/username still 1033 ? I guess that something is wrong
> in my ser.cfg.
> 
> Charles
> 
> My log:
> ------------------------------------------------------------------------------------------------------------------
> SER: SIP Call On-Net section route(2)
> command request 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4
> 192.168.11.4:8000:audio 61.217.225.225 ser.xxx.net.tw local
> 61.229.13.49 remote X-PRO=20build=201082
> info=from:1011 at ser.xxx.net.tw,to:1033 at ser.xxx.net.tw,fromtag:309679536,totag:
> SER: SIP Call On-Net section route(2)
> PDT:prefix2domain: no prefix found in [1033]
> Time:[Tue Feb 22 00:50:57 2005] Method:<INVITE> r-uri:<1033 at ser.xxx.net.tw>
> IP:<61.217.225.225> From:<sip:1011 at ser.xxx.net.tw>
> To:<sip:1033 at ser.xxx.net.tw> <sip:1011 at 192.168.11.4:5060>
> SER: a INT user
> SER: BLIND CALL FORWARDING
> SER: Look aliases
> SER: Look location
> SER isflagset (sip)
> SER: Look aliases
> SER: Look location
> SER isflagset (sip)
> SER: SIP Call On-Net section route(2)
> command request 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4
> 192.168.11.4:8000:audio 61.217.225.225 ser.xxx.net.tw local
> 61.229.13.49 remote X-PRO=20build=201082
> info=from:1011 at ser.xxx.net.tw,to:1033 at ser.xxx.net.tw,fromtag:309679536,totag:
> domain ser.xxx.net.tw doesn't define any mediaproxy.
> will use default mediaproxy for this call.
> command request 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4
> 192.168.11.4:8000:audio 61.217.225.225 ser.xxx.net.tw local
> 61.229.13.49 remote X-PRO=20build=201082
> info=from:1011 at ser.xxx.net.tw,to:1033 at ser.xxx.net.tw,fromtag:309679536,totag:,dispatcher
> session 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4: started.
> listening on xxx.xxx.190.248:35006
> command execution time:  6.19 ms
> forwarding to mediaproxy on /var/run/mediaproxy.sock: got:
> 'xxx.xxx.190.248 35006'
> command execution time: 92.46 ms
> SER: Failure Route section failure_route(1)
> SER: fork to fwdnoanswer
> SER: No Answer Failure and Jump to route(3)
> SER: Demestic Call Off-Net section route(3)
> SER: Connecting to PSTN.....  <================== after this, uri
> should be "0939749xxx at ser.xxx.net.tw" ?????
> command request 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4
> 192.168.11.4:8000:audio 61.217.225.225 ser.xxx.net.tw local
> xxx.xxx.190.243 remote X-PRO=20build=201082
> info=from:1011 at ser.xxx.net.tw,to:1033 at ser.xxx.net.tw,fromtag:309679536,totag:
> domain ser.xxx.net.tw doesn't define any mediaproxy.  <==== this phone
> number should not be 1033, it should be 0939749xxx (a PSTN number)
> ??????
> will use default mediaproxy for this call.
> command request 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4
> 192.168.11.4:8000:audio 61.217.225.225 ser.xxx.net.tw local
> xxx.xxx.190.243 remote X-PRO=20build=201082
> info=from:1011 at ser.xxx.net.tw,to:1033 at ser.xxx.net.tw,fromtag:309679536,totag:,dispatcher
> command execution time:  0.34 ms
> forwarding to mediaproxy on /var/run/mediaproxy.sock: got:
> 'xxx.xxx.190.248 35006'
> command execution time: 3846.84 ms
> PDT:prefix2domain: no prefix found in [1033]
> SER: SIP Call On-Net section route(2)
> session 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4: 0/0/0
> packets, 0/0/0 bytes (caller/called/relayed)
> session 88D1D3FD-0193-41D0-990C-06915D53D1BF at 192.168.11.4: ended (did timeout).
>




More information about the sr-users mailing list