Re: [cisco-voip] Voice traffic over SDWAN
Uh, yeah, it's been a problem in 100% of the cases I've dealt with, especially meraki based sd-wan solutions. to the point that meraki support cannot fix their issue, and asked the customer to disable the full mesh tunneling, in order for sip to work correctly. this is even after the merakis were setup to for voice traffic to use a specific wan link (wan 1) which was the more robust mpls connection. On Thu, Dec 19, 2019 at 2:59 PM Kent Roberts wrote: > I didn’t notice anything different then from the regular wan > > > Kent > > On Dec 19, 2019, at 13:50, Fares Alsaafani wrote: > > > Hi all, > > Did anyone came recently cross deploying or POC voice over SDWAN solution. > I’m looking for thoughts , experiences , tests , things to avoid? > > Fares, > > -- > Best Regards > > *FARES ALSAAFANI* > ___ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > > ___ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Voice traffic over SDWAN
If your SD-WAN solution has packet duplication (aka 0 time failover) my experience is that it tends to work well. Other SD-WAN solutions may work better for VoIP if you can pin SIP/s RTP/sRTP to one side or the other (active/passive over active/active). Depending on the VoIP and SD-WAN scenario, sometimes packets from call session A that started on network path A may end up on network path B in the SD-WAN appliance (when that traffic is load balanced/inspected/classified by the SD-WAN) and that isn’t always tolerated well by some real-time applications (Cisco Expressway can be uniquely sensitive to this). Typical half duplex tcp traffic tolerates this fairly well and the sending/receiving applications may not even notice or see it as minor packet loss and initiate TCP retransmission. Full duplex traffic like media (and by extension real-time applications) generally do not handle that well. Thanks, Ryan On Dec 19, 2019, at 15:59, Kent Roberts wrote: I didn’t notice anything different then from the regular wan Kent On Dec 19, 2019, at 13:50, Fares Alsaafani wrote: Hi all, Did anyone came recently cross deploying or POC voice over SDWAN solution. I’m looking for thoughts , experiences , tests , things to avoid? Fares, -- Best Regards FARES ALSAAFANI ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voipdata=02%7C01%7C%7C3296ba9b901548b0895908d784c66833%7C84df9e7fe9f640afb435%7C1%7C0%7C637123859992078586sdata=AM5nsJ%2FzS%2FzdoV%2BaJvPlleZgMwDFaTNK6w01sHeIhCA%3Dreserved=0 ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Voice traffic over SDWAN
I didn’t notice anything different then from the regular wan Kent > On Dec 19, 2019, at 13:50, Fares Alsaafani wrote: > > > Hi all, > > Did anyone came recently cross deploying or POC voice over SDWAN solution. > I’m looking for thoughts , experiences , tests , things to avoid? > > Fares, > > -- > Best Regards > > FARES ALSAAFANI > ___ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] Voice traffic over SDWAN
Hi all, Did anyone came recently cross deploying or POC voice over SDWAN solution. I’m looking for thoughts , experiences , tests , things to avoid? Fares, -- Best Regards *FARES ALSAAFANI* ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Inbound MGCP call dead-air
Call hits gateway, we do not see proper MGCP set up to CCM... I think the issue is between gateway and ccm. It isn't consistent... maybe 1 out of ever 6-7 calls. Jonathan On Thu, Dec 19, 2019 at 10:24 AM Ryan Huff wrote: > Is this issue on the back of a TN port or anything like that? Have you > engaged the carrier? > > Maybe the gateway is actually working just fine? > > Sent from my iPhone > > On Dec 19, 2019, at 11:01, Jonathan Charles wrote: > > > It is a T1 CAS and the controller is up with no errors it is 1977 > over there. > > > Jonathan > > On Thu, Dec 19, 2019 at 3:03 AM daniele visaggio < > visaggio.dani...@gmail.com> wrote: > >> can you do a "show isdn status" ? >> >> Is the t1 completely up? >> >> Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles < >> jonv...@gmail.com> ha scritto: >> >>> We rebooted the CCM cluster and the problem persisted... >>> >>> Traces show no sign of the call int he calllog... >>> >>> >>> >>> Jonathan >>> >>> On Wed, Dec 18, 2019 at 8:00 PM Ryan Huff wrote: >>> Have you pulled a ccm trace and debug voice ccapi inout, to verif you’re not seeing any weirdness there? “no mgcp / mgcp” has been known to fix weird things; I assume you’ve tried that though. Sent from my iPhone On Dec 18, 2019, at 19:59, Jonathan Charles wrote: Inbound call (to x2475) on an MGCP T1-CAS E Wink Gateway is a 4331 running 16.06.02.SPA, CCM is 11.5.1.2900-21 Get dead air and see no MGCP setup message to CCM, after 60 seconds, call times out (debug vpm signal and mgcp packet, below): 006469: Dec 18 18:23:38.037: htsp_dsp_message: SEND_SIG_STATUS: state=0xC timestamp=35130 systime=1042275951 006470: Dec 18 18:23:38.037: htsp_process_event: [0/1/1:1(21), EM_ONHOOK, E_DSP_SIG_1100]em_onhook_offhook 006471: Dec 18 18:23:38.037: htsp_timer - 50 msec 006472: Dec 18 18:23:38.088: htsp_process_event: [0/1/1:1(21), EM_QUALIFY_SEIZURE, E_HTSP_EVENT_TIMER]em_qualify_seizure_timeouthtsp_setup_ind 006473: Dec 18 18:23:38.088: [0/1/1:1(21)] get_local_station_id calling num= calling name= calling time=12/18 18:23 orig called= 006474: Dec 18 18:23:38.088: htsp_timer - 3000 msec 006475: Dec 18 18:23:38.090: htsp_process_event: [0/1/1:1(21), EM_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]em_wait_setup_ack_get_ack 006476: Dec 18 18:23:38.090: htsp_timer_stop interdigit timer cfgd to 3000 006477: Dec 18 18:23:38.090: htsp_timer2 - 127 msec 006478: Dec 18 18:23:38.217: htsp_process_event: [0/1/1:1(21), EM_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]em_wait_prewink_timer 006479: Dec 18 18:23:38.217: em_offhook (0)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal state = 0x8em_onhook (200)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal state = 0x0 006480: Dec 18 18:23:38.611: htsp_digit_ready: digit = 32 006481: Dec 18 18:23:38.611: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006482: Dec 18 18:23:38.751: htsp_digit_ready: digit = 34 006483: Dec 18 18:23:38.751: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006484: Dec 18 18:23:38.892: htsp_digit_ready: digit = 37 006485: Dec 18 18:23:38.892: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006486: Dec 18 18:23:39.032: htsp_digit_ready: digit = 35 006487: Dec 18 18:23:39.032: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006488: Dec 18 18:23:41.335: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838278 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006489: Dec 18 18:23:41.337: MGCP Packet received from 10.48.41.81:2427 ---> 200 331838278 <--- 006490: Dec 18 18:23:56.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838279 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006491: Dec 18 18:23:56.337: MGCP Packet received from 10.48.41.81:2427 ---> 200 331838279 <--- 006492: Dec 18 18:24:11.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838280 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006493: Dec 18 18:24:11.337: MGCP Packet received from 10.48.41.81:2427 ---> 200 331838280 <--- 006494: Dec 18 18:24:26.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838281 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006495: Dec 18 18:24:26.337: MGCP Packet received from 10.48.41.81:2427 ---> 200 331838281 <--- Configs: controller T1 0/1/1 framing sf clock source line primary linecode ami cablelength long 0db ds0-group 1
Re: [cisco-voip] Inbound MGCP call dead-air
Is this issue on the back of a TN port or anything like that? Have you engaged the carrier? Maybe the gateway is actually working just fine? Sent from my iPhone On Dec 19, 2019, at 11:01, Jonathan Charles wrote: It is a T1 CAS and the controller is up with no errors it is 1977 over there. Jonathan On Thu, Dec 19, 2019 at 3:03 AM daniele visaggio mailto:visaggio.dani...@gmail.com>> wrote: can you do a "show isdn status" ? Is the t1 completely up? Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles mailto:jonv...@gmail.com>> ha scritto: We rebooted the CCM cluster and the problem persisted... Traces show no sign of the call int he calllog... Jonathan On Wed, Dec 18, 2019 at 8:00 PM Ryan Huff mailto:ryanh...@outlook.com>> wrote: Have you pulled a ccm trace and debug voice ccapi inout, to verif you’re not seeing any weirdness there? “no mgcp / mgcp” has been known to fix weird things; I assume you’ve tried that though. Sent from my iPhone On Dec 18, 2019, at 19:59, Jonathan Charles mailto:jonv...@gmail.com>> wrote: Inbound call (to x2475) on an MGCP T1-CAS E Wink Gateway is a 4331 running 16.06.02.SPA, CCM is 11.5.1.2900-21 Get dead air and see no MGCP setup message to CCM, after 60 seconds, call times out (debug vpm signal and mgcp packet, below): 006469: Dec 18 18:23:38.037: htsp_dsp_message: SEND_SIG_STATUS: state=0xC timestamp=35130 systime=1042275951 006470: Dec 18 18:23:38.037: htsp_process_event: [0/1/1:1(21), EM_ONHOOK, E_DSP_SIG_1100]em_onhook_offhook 006471: Dec 18 18:23:38.037: htsp_timer - 50 msec 006472: Dec 18 18:23:38.088: htsp_process_event: [0/1/1:1(21), EM_QUALIFY_SEIZURE, E_HTSP_EVENT_TIMER]em_qualify_seizure_timeouthtsp_setup_ind 006473: Dec 18 18:23:38.088: [0/1/1:1(21)] get_local_station_id calling num= calling name= calling time=12/18 18:23 orig called= 006474: Dec 18 18:23:38.088: htsp_timer - 3000 msec 006475: Dec 18 18:23:38.090: htsp_process_event: [0/1/1:1(21), EM_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]em_wait_setup_ack_get_ack 006476: Dec 18 18:23:38.090: htsp_timer_stop interdigit timer cfgd to 3000 006477: Dec 18 18:23:38.090: htsp_timer2 - 127 msec 006478: Dec 18 18:23:38.217: htsp_process_event: [0/1/1:1(21), EM_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]em_wait_prewink_timer 006479: Dec 18 18:23:38.217: em_offhook (0)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal state = 0x8em_onhook (200)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal state = 0x0 006480: Dec 18 18:23:38.611: htsp_digit_ready: digit = 32 006481: Dec 18 18:23:38.611: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006482: Dec 18 18:23:38.751: htsp_digit_ready: digit = 34 006483: Dec 18 18:23:38.751: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006484: Dec 18 18:23:38.892: htsp_digit_ready: digit = 37 006485: Dec 18 18:23:38.892: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006486: Dec 18 18:23:39.032: htsp_digit_ready: digit = 35 006487: Dec 18 18:23:39.032: htsp_process_event: [0/1/1:1(21), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect 006488: Dec 18 18:23:41.335: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838278 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006489: Dec 18 18:23:41.337: MGCP Packet received from 10.48.41.81:2427---> 200 331838278 <--- 006490: Dec 18 18:23:56.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838279 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006491: Dec 18 18:23:56.337: MGCP Packet received from 10.48.41.81:2427---> 200 331838279 <--- 006492: Dec 18 18:24:11.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838280 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006493: Dec 18 18:24:11.337: MGCP Packet received from 10.48.41.81:2427---> 200 331838280 <--- 006494: Dec 18 18:24:26.336: MGCP Packet sent to 10.48.41.81:2427---> NTFY 331838281 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 X: 0 O: <--- 006495: Dec 18 18:24:26.337: MGCP Packet received from 10.48.41.81:2427---> 200 331838281 <--- Configs: controller T1 0/1/1 framing sf clock source line primary linecode ami cablelength long 0db ds0-group 1 timeslots 1-24 type e description Local T1 CAS ! mgcp mgcp call-agent 10.48.41.80 2427 service-type mgcp version 0.1 mgcp rtp unreachable timeout 1000 action notify mgcp modem passthrough voip mode nse mgcp package-capability mf-package mgcp package-capability rtp-package mgcp package-capability sst-package mgcp package-capability pre-package mgcp package-capability fm-package no mgcp package-capability res-package no mgcp timer receive-rtcp mgcp sdp simple mgcp bind control source-interface GigabitEthernet0/0/0 mgcp bind media source-interface GigabitEthernet0/0/0 mgcp behavior rsip-range tgcp-only mgcp behavior comedia-role none mgcp behavior comedia-check-media-src disable mgcp behavior comedia-sdp-force disable ! ccm-manager
Re: [cisco-voip] Inbound MGCP call dead-air
It is a T1 CAS and the controller is up with no errors it is 1977 over there. Jonathan On Thu, Dec 19, 2019 at 3:03 AM daniele visaggio wrote: > can you do a "show isdn status" ? > > Is the t1 completely up? > > Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles < > jonv...@gmail.com> ha scritto: > >> We rebooted the CCM cluster and the problem persisted... >> >> Traces show no sign of the call int he calllog... >> >> >> >> Jonathan >> >> On Wed, Dec 18, 2019 at 8:00 PM Ryan Huff wrote: >> >>> Have you pulled a ccm trace and debug voice ccapi inout, to verif you’re >>> not seeing any weirdness there? >>> >>> “no mgcp / mgcp” has been known to fix weird things; I assume you’ve >>> tried that though. >>> >>> Sent from my iPhone >>> >>> On Dec 18, 2019, at 19:59, Jonathan Charles wrote: >>> >>> >>> Inbound call (to x2475) on an MGCP T1-CAS E Wink >>> >>> Gateway is a 4331 running 16.06.02.SPA, CCM is 11.5.1.2900-21 >>> >>> Get dead air and see no MGCP setup message to CCM, after 60 seconds, >>> call times out (debug vpm signal and mgcp packet, below): >>> >>> 006469: Dec 18 18:23:38.037: htsp_dsp_message: SEND_SIG_STATUS: >>> state=0xC timestamp=35130 systime=1042275951 >>> 006470: Dec 18 18:23:38.037: htsp_process_event: [0/1/1:1(21), >>> EM_ONHOOK, E_DSP_SIG_1100]em_onhook_offhook >>> 006471: Dec 18 18:23:38.037: htsp_timer - 50 msec >>> 006472: Dec 18 18:23:38.088: htsp_process_event: [0/1/1:1(21), >>> EM_QUALIFY_SEIZURE, >>> E_HTSP_EVENT_TIMER]em_qualify_seizure_timeouthtsp_setup_ind >>> 006473: Dec 18 18:23:38.088: [0/1/1:1(21)] get_local_station_id calling >>> num= calling name= calling time=12/18 18:23 orig called= >>> 006474: Dec 18 18:23:38.088: htsp_timer - 3000 msec >>> 006475: Dec 18 18:23:38.090: htsp_process_event: [0/1/1:1(21), >>> EM_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]em_wait_setup_ack_get_ack >>> 006476: Dec 18 18:23:38.090: htsp_timer_stop interdigit timer cfgd to >>> 3000 >>> 006477: Dec 18 18:23:38.090: htsp_timer2 - 127 msec >>> 006478: Dec 18 18:23:38.217: htsp_process_event: [0/1/1:1(21), >>> EM_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]em_wait_prewink_timer >>> 006479: Dec 18 18:23:38.217: em_offhook >>> (0)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal state >>> = 0x8em_onhook (200)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] >>> set signal state = 0x0 >>> 006480: Dec 18 18:23:38.611: htsp_digit_ready: digit = 32 >>> 006481: Dec 18 18:23:38.611: htsp_process_event: [0/1/1:1(21), >>> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >>> 006482: Dec 18 18:23:38.751: htsp_digit_ready: digit = 34 >>> 006483: Dec 18 18:23:38.751: htsp_process_event: [0/1/1:1(21), >>> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >>> 006484: Dec 18 18:23:38.892: htsp_digit_ready: digit = 37 >>> 006485: Dec 18 18:23:38.892: htsp_process_event: [0/1/1:1(21), >>> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >>> 006486: Dec 18 18:23:39.032: htsp_digit_ready: digit = 35 >>> 006487: Dec 18 18:23:39.032: htsp_process_event: [0/1/1:1(21), >>> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >>> >>> 006488: Dec 18 18:23:41.335: MGCP Packet sent to 10.48.41.81:2427---> >>> NTFY 331838278 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >>> X: 0 >>> O: >>> <--- >>> >>> 006489: Dec 18 18:23:41.337: MGCP Packet received from 10.48.41.81:2427 >>> ---> >>> 200 331838278 >>> <--- >>> >>> 006490: Dec 18 18:23:56.336: MGCP Packet sent to 10.48.41.81:2427---> >>> NTFY 331838279 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >>> X: 0 >>> O: >>> <--- >>> >>> 006491: Dec 18 18:23:56.337: MGCP Packet received from 10.48.41.81:2427 >>> ---> >>> 200 331838279 >>> <--- >>> >>> 006492: Dec 18 18:24:11.336: MGCP Packet sent to 10.48.41.81:2427---> >>> NTFY 331838280 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >>> X: 0 >>> O: >>> <--- >>> >>> 006493: Dec 18 18:24:11.337: MGCP Packet received from 10.48.41.81:2427 >>> ---> >>> 200 331838280 >>> <--- >>> >>> 006494: Dec 18 18:24:26.336: MGCP Packet sent to 10.48.41.81:2427---> >>> NTFY 331838281 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >>> X: 0 >>> O: >>> <--- >>> >>> 006495: Dec 18 18:24:26.337: MGCP Packet received from 10.48.41.81:2427 >>> ---> >>> 200 331838281 >>> <--- >>> >>> Configs: >>> >>> >>> controller T1 0/1/1 >>> framing sf >>> clock source line primary >>> linecode ami >>> cablelength long 0db >>> ds0-group 1 timeslots 1-24 type e >>> description Local T1 CAS >>> ! >>> mgcp >>> mgcp call-agent 10.48.41.80 2427 service-type mgcp version 0.1 >>> mgcp rtp unreachable timeout 1000 action notify >>> mgcp modem passthrough voip mode nse >>> mgcp package-capability mf-package >>> mgcp package-capability rtp-package >>> mgcp package-capability sst-package >>> mgcp package-capability pre-package >>> mgcp package-capability fm-package >>> no mgcp package-capability res-package >>> no mgcp timer receive-rtcp >>> mgcp sdp simple >>> mgcp bind control source-interface GigabitEthernet0/0/0 >>> mgcp bind media source-interface
Re: [cisco-voip] Inbound MGCP call dead-air
can you do a "show isdn status" ? Is the t1 completely up? Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles ha scritto: > We rebooted the CCM cluster and the problem persisted... > > Traces show no sign of the call int he calllog... > > > > Jonathan > > On Wed, Dec 18, 2019 at 8:00 PM Ryan Huff wrote: > >> Have you pulled a ccm trace and debug voice ccapi inout, to verif you’re >> not seeing any weirdness there? >> >> “no mgcp / mgcp” has been known to fix weird things; I assume you’ve >> tried that though. >> >> Sent from my iPhone >> >> On Dec 18, 2019, at 19:59, Jonathan Charles wrote: >> >> >> Inbound call (to x2475) on an MGCP T1-CAS E Wink >> >> Gateway is a 4331 running 16.06.02.SPA, CCM is 11.5.1.2900-21 >> >> Get dead air and see no MGCP setup message to CCM, after 60 seconds, call >> times out (debug vpm signal and mgcp packet, below): >> >> 006469: Dec 18 18:23:38.037: htsp_dsp_message: SEND_SIG_STATUS: state=0xC >> timestamp=35130 systime=1042275951 >> 006470: Dec 18 18:23:38.037: htsp_process_event: [0/1/1:1(21), EM_ONHOOK, >> E_DSP_SIG_1100]em_onhook_offhook >> 006471: Dec 18 18:23:38.037: htsp_timer - 50 msec >> 006472: Dec 18 18:23:38.088: htsp_process_event: [0/1/1:1(21), >> EM_QUALIFY_SEIZURE, >> E_HTSP_EVENT_TIMER]em_qualify_seizure_timeouthtsp_setup_ind >> 006473: Dec 18 18:23:38.088: [0/1/1:1(21)] get_local_station_id calling >> num= calling name= calling time=12/18 18:23 orig called= >> 006474: Dec 18 18:23:38.088: htsp_timer - 3000 msec >> 006475: Dec 18 18:23:38.090: htsp_process_event: [0/1/1:1(21), >> EM_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]em_wait_setup_ack_get_ack >> 006476: Dec 18 18:23:38.090: htsp_timer_stop interdigit timer cfgd to 3000 >> 006477: Dec 18 18:23:38.090: htsp_timer2 - 127 msec >> 006478: Dec 18 18:23:38.217: htsp_process_event: [0/1/1:1(21), >> EM_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]em_wait_prewink_timer >> 006479: Dec 18 18:23:38.217: em_offhook (0)vnm_dsp_set_sig_state:[recEive >> and transMit0/1/1:1(21)] set signal state = 0x8em_onhook >> (200)vnm_dsp_set_sig_state:[recEive and transMit0/1/1:1(21)] set signal >> state = 0x0 >> 006480: Dec 18 18:23:38.611: htsp_digit_ready: digit = 32 >> 006481: Dec 18 18:23:38.611: htsp_process_event: [0/1/1:1(21), >> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >> 006482: Dec 18 18:23:38.751: htsp_digit_ready: digit = 34 >> 006483: Dec 18 18:23:38.751: htsp_process_event: [0/1/1:1(21), >> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >> 006484: Dec 18 18:23:38.892: htsp_digit_ready: digit = 37 >> 006485: Dec 18 18:23:38.892: htsp_process_event: [0/1/1:1(21), >> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >> 006486: Dec 18 18:23:39.032: htsp_digit_ready: digit = 35 >> 006487: Dec 18 18:23:39.032: htsp_process_event: [0/1/1:1(21), >> EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect >> >> 006488: Dec 18 18:23:41.335: MGCP Packet sent to 10.48.41.81:2427---> >> NTFY 331838278 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >> X: 0 >> O: >> <--- >> >> 006489: Dec 18 18:23:41.337: MGCP Packet received from 10.48.41.81:2427 >> ---> >> 200 331838278 >> <--- >> >> 006490: Dec 18 18:23:56.336: MGCP Packet sent to 10.48.41.81:2427---> >> NTFY 331838279 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >> X: 0 >> O: >> <--- >> >> 006491: Dec 18 18:23:56.337: MGCP Packet received from 10.48.41.81:2427 >> ---> >> 200 331838279 >> <--- >> >> 006492: Dec 18 18:24:11.336: MGCP Packet sent to 10.48.41.81:2427---> >> NTFY 331838280 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >> X: 0 >> O: >> <--- >> >> 006493: Dec 18 18:24:11.337: MGCP Packet received from 10.48.41.81:2427 >> ---> >> 200 331838280 >> <--- >> >> 006494: Dec 18 18:24:26.336: MGCP Packet sent to 10.48.41.81:2427---> >> NTFY 331838281 *@ORHC-VG4331-01.orhcnet.local MGCP 0.1 >> X: 0 >> O: >> <--- >> >> 006495: Dec 18 18:24:26.337: MGCP Packet received from 10.48.41.81:2427 >> ---> >> 200 331838281 >> <--- >> >> Configs: >> >> >> controller T1 0/1/1 >> framing sf >> clock source line primary >> linecode ami >> cablelength long 0db >> ds0-group 1 timeslots 1-24 type e >> description Local T1 CAS >> ! >> mgcp >> mgcp call-agent 10.48.41.80 2427 service-type mgcp version 0.1 >> mgcp rtp unreachable timeout 1000 action notify >> mgcp modem passthrough voip mode nse >> mgcp package-capability mf-package >> mgcp package-capability rtp-package >> mgcp package-capability sst-package >> mgcp package-capability pre-package >> mgcp package-capability fm-package >> no mgcp package-capability res-package >> no mgcp timer receive-rtcp >> mgcp sdp simple >> mgcp bind control source-interface GigabitEthernet0/0/0 >> mgcp bind media source-interface GigabitEthernet0/0/0 >> mgcp behavior rsip-range tgcp-only >> mgcp behavior comedia-role none >> mgcp behavior comedia-check-media-src disable >> mgcp behavior comedia-sdp-force disable >> ! >> ccm-manager fallback-mgcp >> ccm-manager redundant-host 10.48.41.81 >> ccm-manager mgcp >> no ccm-manager fax protocol cisco >> ccm-manager
