Jump to content

mathy

Members
  • Posts

    16
  • Joined

  • Last visited

mathy's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. does it possible to use account parameters from a trunk connection as caller id ? cause i need that my ip pbx use sip:account@ipness.com and not sip:username@ipness.com
  2. hi, i have call to ipness to ask why the provider send me a forbidden call and he say me to use codec G729 but when i try to up this codec for this trunk , the codec doesn't move what can i do for force this codec for this trunk ?
  3. yes i'm sure cause when I try with THE SAME ACCOUNT with SAME PARAMETERS on the pbxnsip 2.0.12 ... it work well and with the new it doesn't ... so there is maybe some differance between the two version ...
  4. hi, i'm curently testing the ITSP ipness.net and when i try to make a call from a pbxnsip 2.0.2.1676 , i can make my call with it but when he try the same configuration with ipness on my pbxnsip 3.2.0.3144 i have everytime en error : here is my log from pbxnsip 3.2.0.3144 : [2] 2009/02/10 17:13:20: SIP Rx udp:172.16.1.131:5060: REGISTER sip:bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.131:5060;branch=z9hG4bK-5b20648b From: <sip:528@bizzvoice.bizzdev.net>;tag=902f8fd69473f991o0 To: <sip:528@bizzvoice.bizzdev.net> Call-ID: ee8491a9-742926da@172.16.1.131 CSeq: 10445 REGISTER Max-Forwards: 70 Authorization: Digest username="528",realm="bizzvoice.bizzdev.net",nonce="8987719d17ac270f97e002098c465c59",uri="sip:bizzvoice.bizzdev.net",algorithm=MD5,response="f020b7f901db7b3bf8fed721f6a26156" Contact: <sip:528@172.16.1.131:5060>;expires=3600 User-Agent: Linksys/SPA962-5.2.8(SC) Content-Length: 0 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces [9] 2009/02/10 17:13:20: Resolve 33774: aaaa udp 172.16.1.131 5060 [9] 2009/02/10 17:13:20: Resolve 33774: a udp 172.16.1.131 5060 [9] 2009/02/10 17:13:20: Resolve 33774: udp 172.16.1.131 5060 [2] 2009/02/10 17:13:20: SIP Tx udp:172.16.1.131:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 172.16.1.131:5060;branch=z9hG4bK-5b20648b From: <sip:528@bizzvoice.bizzdev.net>;tag=902f8fd69473f991o0 To: <sip:528@bizzvoice.bizzdev.net>;tag=76b0c49974 Call-ID: ee8491a9-742926da@172.16.1.131 CSeq: 10445 REGISTER Contact: <sip:528@172.16.1.131:5060>;expires=358 Content-Length: 0 [2] 2009/02/10 17:13:21: SIP Rx udp:172.16.1.193:5060: REGISTER sip:bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.193:5060;rport;branch=z9hG4bK768809449 From: <sip:552@bizzvoice.bizzdev.net>;tag=686220153 To: <sip:552@bizzvoice.bizzdev.net> Call-ID: 1778449007@172.16.1.193 CSeq: 812 REGISTER Contact: <sip:552@172.16.1.193:5060> Max-Forwards: 5 User-Agent: Linphone-1.1.0 MX-Video/eXosip Expires: 200 Content-Length: 0 [9] 2009/02/10 17:13:21: Resolve 33775: aaaa udp 172.16.1.193 5060 [9] 2009/02/10 17:13:21: Resolve 33775: a udp 172.16.1.193 5060 [9] 2009/02/10 17:13:21: Resolve 33775: udp 172.16.1.193 5060 [2] 2009/02/10 17:13:21: SIP Tx udp:172.16.1.193:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 172.16.1.193:5060;rport=5060;branch=z9hG4bK768809449 From: <sip:552@bizzvoice.bizzdev.net>;tag=686220153 To: <sip:552@bizzvoice.bizzdev.net>;tag=a5e19bf91d Call-ID: 1778449007@172.16.1.193 CSeq: 812 REGISTER Contact: <sip:552@172.16.1.193:5060>;expires=61 Content-Length: 0 [2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060: INVITE sip:4069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net> Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 101 INVITE Max-Forwards: 70 Contact: <sip:526@172.16.1.104:5060> Expires: 240 User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 399 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 10441819 10441819 IN IP4 172.16.1.104 s=- c=IN IP4 172.16.1.104 t=0 0 m=audio 16398 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv [9] 2009/02/10 17:13:22: UDP: Opening socket on port 57986 [9] 2009/02/10 17:13:22: UDP: Opening socket on port 57987 [5] 2009/02/10 17:13:22: Identify trunk (domain name match) 13 [9] 2009/02/10 17:13:22: Resolve 33776: aaaa udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33776: a udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33776: udp 172.16.1.104 5060 [2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 101 INVITE Content-Length: 0 [9] 2009/02/10 17:13:22: Resolve 33777: aaaa udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33777: a udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33777: udp 172.16.1.104 5060 [2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 101 INVITE User-Agent: pbxnsip-PBX/3.2.0.3144 WWW-Authenticate: Digest realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",domain="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5 Content-Length: 0 [2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060: ACK sip:4069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 101 ACK Max-Forwards: 70 Contact: <sip:526@172.16.1.104:5060> User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 0 [2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060: INVITE sip:4069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net> Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 102 INVITE Max-Forwards: 70 Authorization: Digest username="526",realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",uri="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5,response="1d3f568d529de0be9c4ef3cba77a582c" Contact: <sip:526@172.16.1.104:5060> Expires: 240 User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 399 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 10441819 10441819 IN IP4 172.16.1.104 s=- c=IN IP4 172.16.1.104 t=0 0 m=audio 16398 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv [8] 2009/02/10 17:13:22: Tagging request with existing tag [9] 2009/02/10 17:13:22: Resolve 33778: aaaa udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33778: a udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33778: udp 172.16.1.104 5060 [2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 102 INVITE Content-Length: 0 [9] 2009/02/10 17:13:22: UDP: Opening socket on port 60732 [9] 2009/02/10 17:13:22: UDP: Opening socket on port 60733 [9] 2009/02/10 17:13:22: Resolve 33779: url sip:ipness.net:6060 [9] 2009/02/10 17:13:22: Resolve 33779: a udp ipness.net 6060 [9] 2009/02/10 17:13:22: Resolve 33779: udp 82.146.119.38 6060 [2] 2009/02/10 17:13:22: SIP Tx udp:82.146.119.38:6060: INVITE sip:069665262@ipness.net:6060;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport From: <sip:tilleul@ipness.net:6060>;tag=31120 To: <sip:069665262@ipness.net:6060;user=phone> Call-ID: d399edac@pbx CSeq: 1885 INVITE Max-Forwards: 70 Contact: <sip:tilleul@172.16.1.243:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.2.0.3144 Content-Type: application/sdp Content-Length: 290 v=0 o=- 64964 64964 IN IP4 172.16.1.243 s=- c=IN IP4 172.16.1.243 t=0 0 m=audio 60732 RTP/AVP 0 8 9 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2009/02/10 17:13:22: Resolve 33780: aaaa udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33780: a udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33780: udp 172.16.1.104 5060 [2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 102 INVITE Contact: <sip:526@172.16.1.243:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.2.0.3144 Content-Type: application/sdp Content-Length: 255 v=0 o=- 32019 32019 IN IP4 172.16.1.243 s=- c=IN IP4 172.16.1.243 t=0 0 m=audio 57986 RTP/AVP 0 8 2 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=sendrecv [2] 2009/02/10 17:13:22: SIP Rx udp:82.146.119.38:6060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport From: <sip:tilleul@ipness.net:6060>;tag=31120 To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34 Call-ID: d399edac@pbx CSeq: 1885 INVITE Contact: "Verso CM" <sip:82.146.119.38:6060> Allow-Events: refer User-Agent: pbxnsip-PBX/3.2.0.3144 Content-Length: 0 [2] 2009/02/10 17:13:22: SIP Rx udp:82.146.119.38:6060: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport From: <sip:tilleul@ipness.net:6060>;tag=31120 To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34 Call-ID: d399edac@pbx CSeq: 1885 INVITE Contact: "Verso CM" <sip:82.146.119.38:6060> Allow-Events: refer User-Agent: pbxnsip-PBX/3.2.0.3144 Content-Length: 0 [7] 2009/02/10 17:13:22: Call d399edac@pbx#31120: Clear last INVITE [9] 2009/02/10 17:13:22: Resolve 33781: url sip:ipness.net:6060 [9] 2009/02/10 17:13:22: Resolve 33781: a udp ipness.net 6060 [9] 2009/02/10 17:13:22: Resolve 33781: udp 82.146.119.38 6060 [2] 2009/02/10 17:13:22: SIP Tx udp:82.146.119.38:6060: ACK sip:069665262@ipness.net:6060;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport From: <sip:tilleul@ipness.net:6060>;tag=31120 To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34 Call-ID: d399edac@pbx CSeq: 1885 ACK Max-Forwards: 70 Contact: <sip:tilleul@172.16.1.243:5060;transport=udp> Content-Length: 0 [5] 2009/02/10 17:13:22: INVITE Response 403 Forbidden: Terminate d399edac@pbx [7] 2009/02/10 17:13:22: Other Ports: 1 [7] 2009/02/10 17:13:22: Call Port: fad0a7ad-c2a9bb11@172.16.1.104#865e9b91e7 [9] 2009/02/10 17:13:22: Resolve 33782: aaaa udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33782: a udp 172.16.1.104 5060 [9] 2009/02/10 17:13:22: Resolve 33782: udp 172.16.1.104 5060 [2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 102 INVITE Contact: <sip:526@172.16.1.243:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.2.0.3144 Content-Length: 0 [2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060: ACK sip:4069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1 From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0 To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7 Call-ID: fad0a7ad-c2a9bb11@172.16.1.104 CSeq: 102 ACK Max-Forwards: 70 Authorization: Digest username="526",realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",uri="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5,response="1d3f568d529de0be9c4ef3cba77a582c" Contact: <sip:526@172.16.1.104:5060> User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 0
  5. yes 069 665262 is a valid number that my isdn gateway can reach normaly ... this number is a common number in belgium and my gateway is connected on classic isdn network on belgium so , and bbefore one week , everythink worked fine on this number ....
  6. i have try to reloade an old configuration that working for my gateway and i have always the problem only inbound call work ... every time i try to make a outbound call from that gateway i receive the error forbidden for what cause can i receive a forbidden call ?
  7. yes i use in my dial plan the 9 to make a call to my isdn gateway but it's just a digits that is not use for the number , in the exemple that i use i want to call to 069 665262
  8. Hi everyone, I have a problem with my ISDN gateway (Patton SmartNode 4638-5BRI) sinds 1 week ... ,when i try to make a call from that gateway , i have always the error "forbidden ", but i can receive always call from that gateway and all the other trunks work perfectly for the outbound call... anyone have a idea of this problem ? I don't have make change before 1 month on the voip system (server,gateway,ip phone) ... here is a copy of my log if can help someone to solve the problem and i use pbxnsip 3.0.0.2998 (Win32) : INVITE sip:9069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-cf794530 From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net> Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 101 INVITE Max-Forwards: 70 Contact: <sip:526@172.16.1.104:5060> Expires: 240 User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 399 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 68660036 68660036 IN IP4 172.16.1.104 s=- c=IN IP4 172.16.1.104 t=0 0 m=audio 16410 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv [7] 2009/01/20 14:21:42: UDP: Opening socket on port 61468 [7] 2009/01/20 14:21:42: UDP: Opening socket on port 61469 [5] 2009/01/20 14:21:42: Identify trunk (domain name match) 13 [9] 2009/01/20 14:21:42: Resolve 101602: aaaa udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101602: a udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101602: udp 172.16.1.104 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.104:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-cf794530 From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 101 INVITE Content-Length: 0 [9] 2009/01/20 14:21:42: Resolve 101603: aaaa udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101603: a udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101603: udp 172.16.1.104 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.104:5060: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-cf794530 From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 101 INVITE User-Agent: pbxnsip-PBX/3.0.0.2998 WWW-Authenticate: Digest realm="bizzvoice.bizzdev.net",nonce="e77429a4a3af6a1ecbec81abaebe9ca7",domain="sip:9069665262@bizzvoice.bizzdev.net",algorithm=MD5 Content-Length: 0 [0] 2009/01/20 14:21:42: SIP Rx udp:172.16.1.104:5060: ACK sip:9069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-cf794530 From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 101 ACK Max-Forwards: 70 Contact: <sip:526@172.16.1.104:5060> User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 0 [0] 2009/01/20 14:21:42: SIP Rx udp:172.16.1.104:5060: INVITE sip:9069665262@bizzvoice.bizzdev.net SIP/2.0 Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-d09a6f5c From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net> Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 102 INVITE Max-Forwards: 70 Authorization: Digest username="526",realm="bizzvoice.bizzdev.net",nonce="e77429a4a3af6a1ecbec81abaebe9ca7",uri="sip:9069665262@bizzvoice.bizzdev.net",algorithm=MD5,response="618292a3477d863f9ccbe61a6a9c0a5e" Contact: <sip:526@172.16.1.104:5060> Expires: 240 User-Agent: Linksys/SPA942-6.1.3(a) Content-Length: 399 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 68660036 68660036 IN IP4 172.16.1.104 s=- c=IN IP4 172.16.1.104 t=0 0 m=audio 16410 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv [8] 2009/01/20 14:21:42: Tagging request with existing tag [9] 2009/01/20 14:21:42: Resolve 101604: aaaa udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101604: a udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101604: udp 172.16.1.104 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.104:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-d09a6f5c From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 102 INVITE Content-Length: 0 [7] 2009/01/20 14:21:42: UDP: Opening socket on port 51300 [7] 2009/01/20 14:21:42: UDP: Opening socket on port 51301 [9] 2009/01/20 14:21:42: Resolve 101605: url sip:172.16.1.190 [9] 2009/01/20 14:21:42: Resolve 101605: udp 172.16.1.190 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.190:5060: INVITE sip:069665262@172.16.1.190;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-8beb0a5b78e2e117595d814b20ad0992;rport From: "Mathy Jean-Charles" <sip:069669526@172.16.1.190;user=phone>;tag=57994 To: <sip:069665262@172.16.1.190;user=phone> Call-ID: 6ab844e3@pbx CSeq: 7236 INVITE Max-Forwards: 70 Contact: <sip:069669526@172.16.1.243:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2998 Content-Type: application/sdp Content-Length: 290 v=0 o=- 56814 56814 IN IP4 172.16.1.243 s=- c=IN IP4 172.16.1.243 t=0 0 m=audio 51300 RTP/AVP 0 8 9 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2009/01/20 14:21:42: Resolve 101606: aaaa udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101606: a udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101606: udp 172.16.1.104 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.104:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-d09a6f5c From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 102 INVITE Contact: <sip:526@172.16.1.243:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2998 Content-Type: application/sdp Content-Length: 253 v=0 o=- 9796 9796 IN IP4 172.16.1.243 s=- c=IN IP4 172.16.1.243 t=0 0 m=audio 61468 RTP/AVP 0 8 2 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=sendrecv [0] 2009/01/20 14:21:42: SIP Rx udp:172.16.1.190:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-8beb0a5b78e2e117595d814b20ad0992;rport=5060;received=172.16.1.243 From: "Mathy Jean-Charles" <sip:069669526@172.16.1.190;user=phone>;tag=57994 To: <sip:069665262@172.16.1.190;user=phone> Call-ID: 6ab844e3@pbx CSeq: 7236 INVITE Server: Patton SN4638 5BIS UI 00A0BA03938F R5.1 2008-01-18 H323 SIP BRI M5T SIP Stack/4.0.23.23 Content-Length: 0 [0] 2009/01/20 14:21:42: SIP Rx udp:172.16.1.190:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-8beb0a5b78e2e117595d814b20ad0992;rport=5060;received=172.16.1.243 From: "Mathy Jean-Charles" <sip:069669526@172.16.1.190;user=phone>;tag=57994 To: <sip:069665262@172.16.1.190;user=phone>;tag=2845360344 Call-ID: 6ab844e3@pbx CSeq: 7236 INVITE Contact: <sip:069665262@172.16.1.190:5060> Server: Patton SN4638 5BIS UI 00A0BA03938F R5.1 2008-01-18 H323 SIP BRI M5T SIP Stack/4.0.23.23 Content-Length: 0 [0] 2009/01/20 14:21:42: SIP Rx udp:172.16.1.190:5060: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-8beb0a5b78e2e117595d814b20ad0992;rport=5060;received=172.16.1.243 From: "Mathy Jean-Charles" <sip:069669526@172.16.1.190;user=phone>;tag=57994 To: <sip:069665262@172.16.1.190;user=phone>;tag=2845360344 Call-ID: 6ab844e3@pbx CSeq: 7236 INVITE Server: Patton SN4638 5BIS UI 00A0BA03938F R5.1 2008-01-18 H323 SIP BRI M5T SIP Stack/4.0.23.23 Content-Length: 0 [7] 2009/01/20 14:21:42: Call 6ab844e3@pbx#57994: Clear last INVITE [9] 2009/01/20 14:21:42: Resolve 101607: url sip:069665262@172.16.1.190:5060 [9] 2009/01/20 14:21:42: Resolve 101607: udp 172.16.1.190 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.190:5060: ACK sip:069665262@172.16.1.190:5060 SIP/2.0 Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-8beb0a5b78e2e117595d814b20ad0992;rport From: "Mathy Jean-Charles" <sip:069669526@172.16.1.190;user=phone>;tag=57994 To: <sip:069665262@172.16.1.190;user=phone>;tag=2845360344 Call-ID: 6ab844e3@pbx CSeq: 7236 ACK Max-Forwards: 70 Contact: <sip:069669526@172.16.1.243:5060;transport=udp> Content-Length: 0 [5] 2009/01/20 14:21:42: INVITE Response: Terminate 6ab844e3@pbx [7] 2009/01/20 14:21:42: Other Ports: 1 [7] 2009/01/20 14:21:42: Call Port: ebf34043-c02b625c@172.16.1.104#fcd35cf36c [0] 2009/01/20 14:21:42: SIP Tr udp:172.16.1.104:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-d09a6f5c From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 102 INVITE Contact: <sip:526@172.16.1.243:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2998 Content-Type: application/sdp Content-Length: 253 v=0 o=- 9796 9796 IN IP4 172.16.1.243 s=- c=IN IP4 172.16.1.243 t=0 0 m=audio 61468 RTP/AVP 0 8 2 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=sendrecv [9] 2009/01/20 14:21:42: Resolve 101608: aaaa udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101608: a udp 172.16.1.104 5060 [9] 2009/01/20 14:21:42: Resolve 101608: udp 172.16.1.104 5060 [0] 2009/01/20 14:21:42: SIP Tx udp:172.16.1.104:5060: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-d09a6f5c From: <sip:526@bizzvoice.bizzdev.net>;tag=df437f177e021198o0 To: <sip:9069665262@bizzvoice.bizzdev.net>;tag=fcd35cf36c Call-ID: ebf34043-c02b625c@172.16.1.104 CSeq: 102 INVITE Contact: <sip:526@172.16.1.243:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2998 Content-Length: 0
  9. it's ok with that version ! good job thanks
  10. i will test it tonight so i will give you a feedback tomorrow morning
  11. yes sure ! no problem to hep you OS: windows
  12. when i was in 2.1.8.2463 (Win32) , all my outgoing call work perfectly with my patton gateway smartnode3846 but after a update to 2.1.11.2484 , all my call from bri gateway was cut after 30sec only outgoing call (incoming call work normaly) so i rollback to 2.1.8.2463 andeverything work good .. any issues ??
  13. i found the solution ... : If you like to use "Night Service", you must define a "Service Flag" first. The agent group will is the status of the service flag to determine where to send the call. If the flag is set, the agent group will redirect the calls directly to the "Night Service Number", which can be an internal account or an external number. There is a special pattern "#L" that acts like a service flag (available since version 2.1). If all agents are logged out, then this flag will fire and may redirect all calls to the associated night service number. Please note that you may specify more than one night service flag (seperated by space). In this case the first service flag account corresponds to the first night service number, and the second service flag account corresponds to the second night service number and so on. For example: Service Flag Account: #L Night Service Number: 125 In this example, the PBX would redirect to 125 if all agents are logged out.
  14. hi, i have make a agent group with only one persone (my secretary) , she need the feature queuing cause she have a lot of call in same time ... but when she put his phone on do not distub mode , the redirection on his extension doesn't work ... the caller is never be redirect ... there is an option on agent group to make a redirect on a dnd status or a trick to make it possible ? i'm searcing for an option on agent group like " when no agent is loged on the agent group redirect all to an extension ..." or " when all the agent in the agent groupe are in dnd mode redrect all to an extesion ..."
  15. yes i have followed this tutorial and now i can to call from lcs to pbxnsip but it's doesn't work well (call stop without sound after 3 - 5 sec ) ... yes i have static registred an extention of pbxnsip to the live communication server ( my example: sip:+3269669526@lcs2007-server;transport=tcp on extention 26)
×
×
  • Create New...